Difference between revisions of "HOW-TO:Update a pull request to an official addon repository on GitHub"

From Official Kodi Wiki
Jump to navigation Jump to search
(See also)
m
 
Line 1: Line 1:
{{mininav|[[Add-on development]]}}
A pull request (PR) to an official addon repository (for scripts, plugins or other) on GitHub must have exactly one commit. This is necessary to keep clean commit history in the repo with each commit representing a single addon addition or update. However, you may be asked to make some changes into your PR before it will be submitted. The following procedure allows you to update your PR without creating a new commit:
A pull request (PR) to an official addon repository (for scripts, plugins or other) on GitHub must have exactly one commit. This is necessary to keep clean commit history in the repo with each commit representing a single addon addition or update. However, you may be asked to make some changes into your PR before it will be submitted. The following procedure allows you to update your PR without creating a new commit:


Line 18: Line 21:
=== See also ===
=== See also ===
* [[HOW-TO:Create add-on PRs using Git Subtree Merging]]
* [[HOW-TO:Create add-on PRs using Git Subtree Merging]]
[[Category:Add-on_development]]

Latest revision as of 09:39, 17 December 2020

Home icon grey.png   ▶ Add-on development ▶ HOW-TO:Update a pull request to an official addon repository on GitHub


A pull request (PR) to an official addon repository (for scripts, plugins or other) on GitHub must have exactly one commit. This is necessary to keep clean commit history in the repo with each commit representing a single addon addition or update. However, you may be asked to make some changes into your PR before it will be submitted. The following procedure allows you to update your PR without creating a new commit:

1. Make all necessary changes in your addon PR.

2. Commit your changes to the PR branch using the following commands:

git add .
git commit -a --amend --no-edit

3. Push your changes to GitHub. Since you have rewritten the commit history you need to use --force option:

git push -f

Now you PR will be updated and you still have one commit in the PR.

N.B. It is advisable to only update or push one addon at one time and wait til the request has completed before pushing the next update.

See also