Confirmed users
4,971
edits
ReleaseEngineering/How To/VCSSync: Difference between revisions
Jump to navigation
Jump to search
ReleaseEngineering/How To/VCSSync (view source)
Revision as of 20:39, 14 October 2013
, 14 October 2013→How to deal with completely resetting gecko-projects
| Line 25: | Line 25: | ||
=== How to deal with completely resetting gecko-projects === | === How to deal with completely resetting gecko-projects === | ||
# Make the decision that this is the solution to the problem. | |||
# Make sure people are aware this is going to happen. | |||
# Stop the conversion of gecko-projects. This is currently on vcs2vcs@vcssync2, and is run via cron. | # Stop the conversion of gecko-projects. This is currently on vcs2vcs@vcssync2, and is run via cron. | ||
# Save a copy of https://raw.github.com/mozilla/integration-gecko-projects/master/README.md | # Save a copy of https://raw.github.com/mozilla/integration-gecko-projects/master/README.md | ||
# Delete the repo! This option is available in the "Danger Zone" area of https://github.com/mozilla/integration-gecko-projects/settings | |||
TODO | # Recreate the repo. There's a "Create a new repo" icon in the top right. This will need the same name, should be public, and you want to initialize the repo with a README. | ||
# Edit the README with the contents you downloaded in step 4. | |||
# Start the conversion back up. You may only need to delete the build/target and build/stage_source/BAD_REPO directories. Or you may need to blow away the whole thing from orbit to be sure, in which case you should follow the docs for ____ TODO | |||
=== How to deal with GECKO90_2011121217_RELBRANCH === | === How to deal with GECKO90_2011121217_RELBRANCH === | ||