EngineeringProductivity/HowTo/MirrorRepo: Difference between revisions

Jump to navigation Jump to search
(→‎Steps to mirror mozbase: note changeset hash)
Line 15: Line 15:
# Test your changes to make sure you didn't break the build using [https://wiki.mozilla.org/ReleaseEngineering/TryServer TryServer].
# Test your changes to make sure you didn't break the build using [https://wiki.mozilla.org/ReleaseEngineering/TryServer TryServer].
# Get the attachment it reviewed, pushed to try and landed on mozilla-inbound. When mozilla-inbound is merged to m-c this bug can be marked fixed.  Make sure your m-c commit message references the mozbase commit hash.
# Get the attachment it reviewed, pushed to try and landed on mozilla-inbound. When mozilla-inbound is merged to m-c this bug can be marked fixed.  Make sure your m-c commit message references the mozbase commit hash.
# Create a git tag called 'mozilla-central' on your commit, you'll need to delete the old 'mozilla-central' tag. This way, the changeset tagged 'mozilla-central' will always keep track of the current state of mozbase in m-c.  Use the URL of the mozilla-central changeset hash:
# Create a git tag called 'mozilla-central' on your commit, you'll need to delete the old 'mozilla-central' tag. This way, the changeset tagged 'mozilla-central' will always keep track of the current state of mozbase in m-c.  Use the URL of the mozilla-central changeset hash as the tag commit message:
<pre>
<pre>
git pull --tags git@github.com:mozilla/mozbase.git master
git pull --tags git@github.com:mozilla/mozbase.git master
947

edits

Navigation menu