Difference between revisions of "Commiting Changes"
Binarymaster (talk | contribs) (→For newbies: multiple Pull Requests) |
Binarymaster (talk | contribs) (→For newbies: improve) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
==For newbies== | ==For newbies== | ||
To commit your changes into the repository, follow these steps: | To commit your changes into the repository, follow these steps: | ||
| − | # ''Fork'' the ReactOS repository into your own GitHub account | + | # If you don't have [http://github.com/ GitHub] account, create it first |
| + | # ''Fork'' the [http://github.com/reactos/reactos ReactOS repository] into your own GitHub account | ||
# Make sure you set up your ''full name'' and correct ''public e-mail'' in your [https://github.com/settings/profile account settings] (this is required by our [https://github.com/reactos/reactos/blob/master/CONTRIBUTING.md#rules-and-recommendations contributing rules]) | # Make sure you set up your ''full name'' and correct ''public e-mail'' in your [https://github.com/settings/profile account settings] (this is required by our [https://github.com/reactos/reactos/blob/master/CONTRIBUTING.md#rules-and-recommendations contributing rules]) | ||
# ''Commit'' changes in your new forked repository following our [https://github.com/reactos/reactos/blob/master/.gitmessage commit message style] | # ''Commit'' changes in your new forked repository following our [https://github.com/reactos/reactos/blob/master/.gitmessage commit message style] | ||
| Line 11: | Line 12: | ||
==For developers== | ==For developers== | ||
Please follow [[ReactOS Git For Dummies#Workflow|Workflow]] guide. | Please follow [[ReactOS Git For Dummies#Workflow|Workflow]] guide. | ||
| + | |||
| + | ==Maintainers== | ||
| + | There are known maintainers for some modules and parts of the ReactOS: | ||
| + | |||
| + | * https://github.com/reactos/reactos/blob/master/MAINTAINERS | ||
| + | |||
| + | Once you have created a Pull Request, you may want to communicate with module maintainer for review and merge your code. | ||
==See also== | ==See also== | ||
| − | For further details read [[ReactOS Git For Dummies]] article. | + | * For further details read [[ReactOS Git For Dummies]] article. |
| + | * You may also refer to older article [[Submitting Patches]]. | ||
[[Category: Tutorial]] | [[Category: Tutorial]] | ||
Revision as of 13:47, 4 February 2020
Since the migration to GitHub, contributing to the project become even easier!
For newbies
To commit your changes into the repository, follow these steps:
- If you don't have GitHub account, create it first
- Fork the ReactOS repository into your own GitHub account
- Make sure you set up your full name and correct public e-mail in your account settings (this is required by our contributing rules)
- Commit changes in your new forked repository following our commit message style
- If you already have a pending Pull Request and you want to create another, you should create a new branch in your forked repository and commit changes to it
- Create a Pull Request from your branch using either GitHub interface or GitHub Desktop App
For developers
Please follow Workflow guide.
Maintainers
There are known maintainers for some modules and parts of the ReactOS:
Once you have created a Pull Request, you may want to communicate with module maintainer for review and merge your code.
See also
- For further details read ReactOS Git For Dummies article.
- You may also refer to older article Submitting Patches.
