Skip to content

Commit d6d8fd1

Browse files
authored
Add example of how to sync two git repositories
1 parent b5fe355 commit d6d8fd1

File tree

1 file changed

+18
-5
lines changed

1 file changed

+18
-5
lines changed

RELEASING.md

Lines changed: 18 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,11 +15,24 @@ Only repo administrator is allowed to run the release script, otherwise it will
1515
Prior to making a release,
1616

1717
1. Sync any changes that have been merged to backup-utils-private into this repository.
18-
1. Go through the list of open pull requests and merge any that are ready for merging.
19-
1. Go through the list of closed pull requests since the last release and ensure those that should be included in the release notes:
20-
- have a "bug", "enhancement" or "feature" label,
21-
- have a title that clearly describes the changes in that pull request. Reword if necessary.
22-
1. Perform a dry run (add `--dry-run` to one of the commands below) and verify the version strings are going to be changed and verify the release notes.
18+
19+
One possible way to accomplish this is to add the other repository as a remote and merge the changes from the default branch of that remote.
20+
```
21+
git clone [email protected]:github/backup-utils
22+
cd backup-utils
23+
git checkout master
24+
git checkout -b sync-private-to-public
25+
git remote add private <private-repo>
26+
git fetch private
27+
git merge private/master
28+
git push origin HEAD
29+
```
30+
Then open a pull request on this repository with the changes.
31+
2. Go through the list of open pull requests and merge any that are ready for merging.
32+
3. Go through the list of closed pull requests since the last release and ensure those that should be included in the release notes:
33+
- have a "bug", "enhancement" or "feature" label,
34+
- have a title that clearly describes the changes in that pull request. Reword if necessary.
35+
4. Perform a dry run (add `--dry-run` to one of the commands below) and verify the version strings are going to be changed and verify the release notes.
2336

2437
## Automatic Process from chatops (internal to GitHub only)
2538

0 commit comments

Comments
 (0)