Skip to content

Commit cec73cc

Browse files
author
kiaralee
committed
Initial commit
1 parent ae89631 commit cec73cc

32 files changed

+42278
-0
lines changed

‎.env.example

+7
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
REACT_APP_apiKey=
2+
REACT_APP_authDomain=
3+
REACT_APP_projectId=
4+
REACT_APP_storageBucket=
5+
REACT_APP_messagingSenderId=
6+
REACT_APP_appId=
7+
REACT_APP_measurementId=

‎.github/CODEOWNERS

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
* @hightechu/staff

‎.github/CONTRIBUTING.md

+26
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Contributing
2+
3+
This projects encourages contributions of all forms (source code, documentation, improvements, bug reporting, etc.).
4+
5+
By participating in this project, you agree to this projects [`code of conduct`](../CODE_OF_CONDUCT.md).
6+
7+
## Getting Started
8+
9+
To learn how to get a local development environment started visit the [`getting started`](../GETTING_STARTED.md) document.
10+
11+
## Submit a Pull Request
12+
13+
At this point, you have made your contribution to a new branch based off of `main` and are ready to create a Pull Request. Create a Pull Request from your branch to the `main` branch and add any relevant information.
14+
15+
Please include a description of your contribution, any tests you've written, a screenshot of the feature, etc. The more descriptive your Pull Request is the higher the chances are that it will be merged into `main`.
16+
17+
## Contribution
18+
19+
Here are a few things that will improve your chances of your Pull Request being accepted:
20+
21+
* Write Tests.
22+
* Write Good Commit Messages.
23+
* Document Your Code.
24+
* Update Documentation.
25+
* Follow Coding Conventions.
26+
* Write Clean Code.

‎.github/pull_request_template.md

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Description
2+
<!-- Please include a summary of the change(s) and the relevant issue number if applicable.
3+
Answer: What did you do? How does it work? If this was a bug fix, what was the bug? -->
4+
5+
## Checklist
6+
7+
- [ ] The code follows all style guidelines. <!-- Is the code clean and formatted correctly? -->
8+
- [ ] The code passes all required tests. <!-- Did you test the code in the local environment? -->
9+
- [ ] The code is documented. <!-- As needed, did you add this function to the help page? -->
10+
- [ ] I have self-reviewed my changes and have done QA. <!-- Is the code working and high-quality? -->
11+
12+
## General Comments
13+
<!-- Optional - Add anything else you would like to add to the Pull Request -->

‎.github/workflows/firebase.yml

+52
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
name: Firebase CI
2+
3+
on:
4+
push:
5+
branches: [ main ]
6+
pull_request:
7+
branches: [ main]
8+
9+
jobs:
10+
build:
11+
12+
runs-on: ubuntu-latest
13+
14+
strategy:
15+
matrix:
16+
node-version: [14.x]
17+
18+
steps:
19+
- uses: actions/checkout@v2
20+
- name: Use Node.js ${{ matrix.node-version }}
21+
uses: actions/setup-node@v1
22+
with:
23+
node-version: ${{ matrix.node-version }}
24+
- run: npm install -g npm
25+
- name: npm install, build and test
26+
run: |
27+
npm install
28+
npm run build
29+
- name: Archive Build
30+
uses: actions/upload-artifact@v2
31+
with:
32+
name: build
33+
path: build
34+
35+
deploy:
36+
name: Deploy
37+
needs: build
38+
runs-on: ubuntu-latest
39+
40+
steps:
41+
- uses: actions/checkout@v2
42+
- name: Download Build
43+
uses: actions/download-artifact@v2
44+
with:
45+
name: build
46+
path: build
47+
- name: Deploy to Firebase
48+
uses: w9jds/firebase-action@master
49+
with:
50+
args: deploy --only hosting
51+
env:
52+
FIREBASE_TOKEN: ${{ secrets.FIREBASE_TOKEN }}

‎.gitignore

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
2+
3+
# dependencies
4+
/node_modules
5+
/.pnp
6+
.pnp.js
7+
8+
# testing
9+
/coverage
10+
11+
# production
12+
/build
13+
14+
# misc
15+
.DS_Store
16+
.env.local
17+
.env.development.local
18+
.env.test.local
19+
.env.production.local
20+
.env
21+
22+
npm-debug.log*
23+
yarn-debug.log*
24+
yarn-error.log*

‎CODE_OF_CONDUCT.md

+128
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
[email protected].
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

‎README.md

+40
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# HighTechU Techccelerator React App
2+
3+
## About
4+
5+
<!-- You will want to modify the text below to include a short description of your app -->
6+
<!-- You will want to modify the documentation link to your app's help page -->
7+
8+
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Tortor vitae purus faucibus ornare suspendisse sed nisi lacus. Posuere lorem ipsum dolor sit. Quis varius quam quisque id diam vel quam elementum pulvinar. Rhoncus dolor purus non enim praesent elementum facilisis leo. Accumsan lacus vel facilisis volutpat est velit egestas dui. For more information about the app visit the "[documentation](https://hightechu.ca)".
9+
10+
11+
## Technologies
12+
13+
The HighTechU Techccelerator web app uses the following technologies: Node.js, React.js, Firebase, and Bootstrap.
14+
15+
## Getting Started
16+
17+
To get started with the project visit the [`getting started`](docs/GETTING_STARTED.md) documentation. The document outlines how to get a copy running locally/publicly and how to setup the app.
18+
19+
## Contributing
20+
21+
Contributions are always welcome!
22+
23+
See [`CONTRIBUTING`](.github/CONTRIBUTING.md) for ways to get started.
24+
25+
Please adhere to this project's [`code of conduct`](CODE_OF_CONDUCT.md).
26+
27+
## Useful Resources
28+
29+
* [React Documentation](https://react.dev/reference/react)
30+
* [Firebase Documentation](https://firebase.google.com/docs?gad=1&gclid=Cj0KCQjwzdOlBhCNARIsAPMwjbzPQ-Agmh5XfsQcmfi5jzcgb5lp9x1lHb9xjZqGsFUmLq4MXlq2CqYaAnlIEALw_wcB&gclsrc=aw.ds)
31+
32+
## License
33+
34+
The project uses the [MIT LICENSE](https://choosealicense.com/licenses/mit/).
35+
36+
## Authors
37+
38+
<!-- You will want modify the authors list below to include all contributing team members. -->
39+
40+
- [@hightechu](https://github.com/hightechu)

0 commit comments

Comments
 (0)