Sync or delete an outdated fork before contributing
2 minute read
The first time you make a contribution to the documentation by way of GitHub or Netlify CMS, this creates a copy (fork) of the axway-open-docs repository in your GitHub account.
Since there are other users collaborating with Axway documentation, it is highly likely that your fork will quickly fall behind the upstream repository and you might encounter conflicts the next time you try to send a pull request.
NoteYou do not need to sync your fork if you are working exclusively from Netlify CMS, as Netlify CMS creates the new branch based on master from the upstream repository.
Delete and recreate your fork
CautionDo not delete your fork if you have pending PRs that have not yet been merged, as the changes from those PRs will be lost.
To delete and recreate your fork before you make a new contribution:
Go to your
axway-open-docsfork on GitHub, and click Settings
Under Danger Zone, click Delete this repository.
Follow the Edit on GitHub procedure to start a new contribution, which creates a new fork based on the latest upstream.
To find out more about how to delete your fork, see Deleting a repository.
Sync your fork
You can sync your fork with the latest changes added to the upstream repository, using Git on the command line. For details, see Keep your fork synced.
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.