On the third step you will be given a unique link to log into the Developer Portal, to create a `Conduit API Token`. This
token will be used to allow the CLI `arc` utility to communicate with Phabricator.
## Creating the patch
For every file you change or add, you must let git know about them:
```
git add someFile
```
For files that must be removed, you must do so using git:
```
git rm someFile
```
Likewise, for renaming a file, you must do so via git:
```
git mv someFile someFileName2
```
Once you're happy with your change, and you have verified locally that it works by having first built and
installed it, it's time to commit your changes.
```
git commit
```
Make sure you provide a meaningful summary and a separate body to your commit message. For more information
on suitable commit messages, please check the [tooling central documentation](https://github.com/solus-project/tooling-central/blob/master/README.rst#using-git).
If you want to link this patch to an issue on the Developer portal, simply mention it in your commit message:
```
The inclusion of <somepackage> fixes T1234
```
If you need a change to depend on another change, mention it in the commit message too:
```
Depends on D5
```
Now you have your git commit, it's time to send it to us for review. Using the CLI again, simply issue:
```
arc diff
```
A new editor session will open, where you can provide optional details. Note that the default reviewer will
be assigned after you submit, so it is not necessary to specify anyone here. Once you're finished, save and
exit the editor (`CTRL+O` + `CTRL+X` for nano), and the patch will then be uploaded. You'll be presented
with the Differential URL, and a review will happen as soon as possible.
## Fixing a patch that needs changes
That's easy. Don't make a new commit, just make any relevant changes to your local tree, adding + removing as
Submission directly to a repository is only possible for maintainers. As a maintainer you may freely push to your package(s) and initiate builds for them, which will be pushed to the unstable repository. You can watch
To request maintainer rights for a repository, it is expected that some level of contribution/maintenance has already happened by way of testing/patching, and there is reasonable trust demonstrated to "hand the keys"
Currently, the request mechanism [contact Ikey on IRC](/articles/contributing/getting-involved/en). It is far easier to grant access to active community members than those unknown to the project.
