Contributing to Quevent

December 16, 2019 · View on GitHub

Code of Conduct
Issues and Bugs
Submitting a Pull Request

Code of Conduct

Help us keep Angular open and inclusive. Please read and follow our Code of Conduct.

Found a Bug?

If you find a bug in the source code, you can help us by submitting an issue to our GitHub Repository. Even better, you can submit a Pull Request with a fix.

Submitting a Pull Request (PR)

Select or create an issue
Fork the repo
Create a new branch using the following format git checkout -b feature/#${ISSUE_NUMBER}-${ISSUE_TITLE}
```
# Example
git checkout -b feature/#55-new-issue
```

Use the issue references keywords More information

# Example
feat: New issue finished
  - Testing
  - Testing
Resolve: #55

In GitHub, send a pull request to sjdonado/quevent:master.

If we suggest changes then:
- Make the required updates.
- Re-run the Angular test suites to ensure tests are still passing.
- Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
```
git rebase master -i
git push -f
```

Rebase your branch and force push to your GitHub repository (this will update your Pull Request):
```
git rebase master -i
git push -f
```

That's it! Thank you for your contribution!

After your pull request is merged

After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository:

Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
```
git push origin --delete my-fix-branch
```
Check out the master branch:
```
git checkout master -f
```
Delete the local branch:
```
git branch -D my-fix-branch
```
Update your master with the latest upstream version:
```
git pull --ff upstream master
```