|
| 1 | +# Contributing to CoCreate-url-uploader |
| 2 | + |
| 3 | +This project is work of [many contributors](https://github.com/CoCreate-app/CoCreate-url-uploader/graphs/contributors). |
| 4 | +You're encouraged to submit [pull requests](https://github.com/CoCreate-app/CoCreate-url-uploader/pulls), |
| 5 | +[propose features and discuss issues](https://github.com/CoCreate-app/CoCreate-url-uploader/issues). |
| 6 | + |
| 7 | +In the examples below, substitute your Github username for `contributor` in URLs. |
| 8 | + |
| 9 | +## Fork the Project |
| 10 | + |
| 11 | +Fork the [project on Github](https://github.com/CoCreate-app/CoCreate-url-uploader) and check out your copy. |
| 12 | + |
| 13 | +``` |
| 14 | +git clone https://github.com/contributor/CoCreate-url-uploader.git |
| 15 | +cd CoCreate-url-uploader |
| 16 | +git remote add upstream https://github.com/CoCreate-app/CoCreate-url-uploader.git |
| 17 | +``` |
| 18 | + |
| 19 | +## Create a Topic Branch |
| 20 | + |
| 21 | +Make sure your fork is up-to-date and create a topic branch for your feature or bug fix on dev branch. |
| 22 | + |
| 23 | +``` |
| 24 | +git checkout dev |
| 25 | +git pull upstream dev |
| 26 | +git checkout -b my-feature-branch |
| 27 | +``` |
| 28 | + |
| 29 | +## Write Tests |
| 30 | + |
| 31 | +Try to write a test that reproduces the problem you're trying to fix or describes a feature that you want to build. |
| 32 | + |
| 33 | +We definitely appreciate pull requests that highlight or reproduce a problem, even without a fix. |
| 34 | + |
| 35 | +## Write Code |
| 36 | + |
| 37 | +Implement your feature or bug fix. |
| 38 | + |
| 39 | +## Write Documentation |
| 40 | + |
| 41 | +Document any external behavior in the [README](README.md). |
| 42 | + |
| 43 | +## Commit Changes |
| 44 | + |
| 45 | +Make sure git knows your name and email address: |
| 46 | + |
| 47 | +``` |
| 48 | +git config --global user.name "Your Name" |
| 49 | +git config --global user.email "[email protected]" |
| 50 | +``` |
| 51 | + |
| 52 | +We use [semantic-release](https://github.com/semantic-release/semantic-release) as process to generate changelog |
| 53 | +and to release. Write meaningful commits according to |
| 54 | +[Commit Message Formats](https://github.com/semantic-release/semantic-release#commit-message-format) is important. |
| 55 | + |
| 56 | +``` |
| 57 | +git add ... |
| 58 | +git commit -am "commit-type(optional topic): a meaningful message" |
| 59 | +``` |
| 60 | + |
| 61 | +Here is an example of the release type that should be done based on a [semantic-release](https://github.com/semantic-release/semantic-release): |
| 62 | + |
| 63 | +| Commit message | Release type | |
| 64 | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -------------------------- | |
| 65 | +| `fix(pencil): stop graphite breaking when too much pressure applied` | Patch Release | |
| 66 | +| `feat(pencil): add 'graphiteWidth' option` | ~~Minor~~ Feature Release | |
| 67 | +| `perf(pencil): remove graphiteWidth option`<br><br>`BREAKING CHANGE: The graphiteWidth option has been removed.`<br>`The default graphite width of 10mm is always used for performance reasons.` | ~~Major~~ Breaking Release | |
| 68 | + |
| 69 | +## Push |
| 70 | + |
| 71 | +``` |
| 72 | +git push origin my-feature-branch |
| 73 | +``` |
| 74 | + |
| 75 | +## Make a Pull Request |
| 76 | + |
| 77 | +Go to [https://github.com/CoCreate-app/CoCreate-url-uploader](https://github.com/CoCreate-app/CoCreate-url-uploader) and select your feature branch. |
| 78 | +Click the 'Pull Request' button and fill out the form. Pull requests are usually reviewed within a few days. |
| 79 | + |
| 80 | +## Rebase |
| 81 | + |
| 82 | +If you've been working on a change for a while, rebase with upstream/dev. |
| 83 | + |
| 84 | +``` |
| 85 | +git fetch upstream |
| 86 | +git rebase upstream/dev |
| 87 | +git push origin my-feature-branch -f |
| 88 | +``` |
| 89 | + |
| 90 | +## Be Patient |
| 91 | + |
| 92 | +It's likely that your change will not be merged and that the nitpicky maintainers will ask you to do more, or fix seemingly benign problems. Hang in there! |
| 93 | + |
| 94 | +## Thank You |
| 95 | + |
| 96 | +Please do know that we really appreciate and value your time and work. We love you, really. |
0 commit comments