|
1 | 1 | Pull Requests |
2 | 2 | ------------- |
3 | 3 |
|
4 | | -If you're thinking about making some changes, maybe fixing a bug, or adding a |
5 | | -snazzy new feature, first, thank you. Contributions are very welcome. Things |
6 | | -need to be manageable for the maintainers, however. So below you'll find **The |
| 4 | +If you're thinking about making some changes, maybe fixing a bug, or adding a |
| 5 | +snazzy new feature, first, thank you. Contributions are very welcome. Things |
| 6 | +need to be manageable for the maintainers, however. So below you'll find **The |
7 | 7 | fastest way to get your pull request merged in.** Some things, particularly how |
8 | 8 | you set up your branches and work with git, are just suggestions, but pretty good |
9 | 9 | ones. |
|
14 | 14 |
|
15 | 15 | git remote add base git://github.com/jsdoc3/jsdoc.git |
16 | 16 |
|
17 | | - Here 'base' is the name of the remote. Feel free to use whatever you want. |
| 17 | + Here 'base' is the name of the remote. Feel free to use whatever you want. |
18 | 18 |
|
19 | 19 | 2. **Set up a tracking branch for the base repository** |
20 | 20 | We're gonna call this your ```<tracking branch>```. You will only ever update |
|
64 | 64 | links it. |
65 | 65 |
|
66 | 66 | If it's a feature, provide some context about the motivations behind the feature, |
67 | | - why it's important/useful/cool/necessary and what it does/how it works. Don't |
| 67 | + why it's important/useful/cool/necessary and what it does/how it works. Don't |
68 | 68 | worry about being too verbose. Folks will be much more amenable to reading through |
69 | 69 | your code if they know what its supposed to be about. |
0 commit comments