sdth-site

所属分类:教育系统应用
开发工具:JavaScript
文件大小:0KB
下载次数:0
上传日期:2023-01-11 20:30:54
上 传 者sh-1993
说明:  圣地亚哥科技中心网站
(San Diego Tech Hub website)

文件列表:
.editorconfig (207, 2019-12-06)
.eslintrc.js (1688, 2019-12-06)
.nvmrc (7, 2019-12-06)
CODE_OF_CONDUCT.md (3357, 2019-12-06)
LICENSE (1076, 2019-12-06)
__mocks__/ (0, 2019-12-06)
__mocks__/file-mock.js (34, 2019-12-06)
__mocks__/gatsby.js (445, 2019-12-06)
env.default (133, 2019-12-06)
gatsby-config.js (3562, 2019-12-06)
gatsby-node.js (4700, 2019-12-06)
jest.config.js (1052, 2019-12-06)
package-lock.json (1032585, 2019-12-06)
package.json (3685, 2019-12-06)
src/ (0, 2019-12-06)
src/components/ (0, 2019-12-06)
src/components/404/ (0, 2019-12-06)
src/components/404/index.js (870, 2019-12-06)
src/components/about/ (0, 2019-12-06)
src/components/about/index.js (4163, 2019-12-06)
src/components/about/styles.js (2920, 2019-12-06)
src/components/avatar-card/ (0, 2019-12-06)
src/components/avatar-card/index.js (313, 2019-12-06)
src/components/calendar/ (0, 2019-12-06)
src/components/calendar/details.js (1816, 2019-12-06)
src/components/calendar/index.js (1644, 2019-12-06)
src/components/calendar/styles.css (1659, 2019-12-06)
src/components/calendar/styles.js (1302, 2019-12-06)
src/components/code-of-conduct/ (0, 2019-12-06)
src/components/code-of-conduct/index.js (916, 2019-12-06)
src/components/common/ (0, 2019-12-06)
src/components/common/ErrorMsg.js (196, 2019-12-06)
src/components/common/ExternalLink.js (453, 2019-12-06)
src/components/common/Html.js (171, 2019-12-06)
... ...

# San Diego Tech Hub Site [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat-square)](http://makeapullrequest.com) This site was developed with [GatsbyJS](https://www.gatsbyjs.org/) and serves as the home page for [San Diego Tech Hub](https://sandiegotechhub.com). ## Contribute **Working on your first Pull Request?** You can learn how from this _free_ series [How to Contribute to an Open Source Project on GitHub](https://egghead.io/series/how-to-contribute-to-an-open-source-project-on-github) ### System Requirements - [git](https://git-scm.com/downloads) - [node](https://nodejs.org/en/download) - [nvm](https://github.com/nvm-sh/nvm) ### Getting Started 1. Fork the project (this copies the SDTH Website repository to your GitHub account) ![Fork The Project](src/images/readme/forkbutton.png) 2. Clone your fork (copies your GitHub SDTH Website repository to your local computer) > `git clone https://github.com/[your-github-username]/sdth-site.git` 3. Confirm you are in the right directory in terminal: `cd sdth-site` 4. Add an `upstream` remote for keeping your local repository up-to-date > `git remote add upstream https://github.com/san-diego-tech-hub/sdth-site.git` 5. Run `cp env.default .env.dev` 6. Grab the environment variables from a developer in the [slack channel](https://join.slack.com/t/sandiegotechhub/shared_invite/enQtNTI1MDA2NjQyNDcwLTRhYmFhOGZlNzQyZWQ0NmJjMTEzNGE1YjI1NTJmY2RhZjVmYjBjNDAyYmI4MDZkNTM4MzMwM2JmYWQzOGVkYjY) 7. Run `nvm use` use the version of node identified in `.nvmrc` 8. Run `npm ci` to install the project dependencies 9. Run `npm start` to start your dev environment ### Creating a new pull request 1. Make sure you are on the `development` branch, and you have pulled the latest changes > `git checkout development && git pull upstream development` 2. Install any new dependencies: `npm ci` 3. Create a new branch off of the `development` branch > `git checkout -b [NEW BRANCH NAME]` > **Branch naming conventions:** `fix/[BRANCH]` for bug fixes, `feature/[BRANCH]` for new features, `dev/[BRANCH]` for non-user-facing changes. The `[BRANCH]` portion should be kebab case. For example, if you want to update the README.md file, your branch could be called `dev/update-readme` 4. Make changes and commit them. `git add . && git commit -m "[YOUR COMMIT MESSAGE]"` > The subject of a commit message (the first line) should be 72 characters or less. If you need more room for a longer explanation of your changes, you can add a blank line below the subject and write a commit body. The commit message should be in present-imperative tense ("Update README.md" rather than "Updates" or "Updated"). 5. Push your branch to your fork: `git push -u origin [BRANCH NAME]` 6. Open a new pull request against the `development` branch from your fork using the GitHub user interface

近期下载者

相关文件


收藏者