Skip to content

[July 30, 2019] GitHub Migration

Siming Yuan edited this page Jul 31, 2019 · 3 revisions

On July 30, 2019, we've made some changes to the master/dev branch of this repository.

Prior to this date, whilst the content of this repo was 100% the same as that of the development repository internally in Cisco, the commit IDs did not line up - this repo was a copy, not a clone.

As part of this migration effort, we've re-aligned the actual branch commit ID. You can now see the development history of this repository, with the thousands of commits from our developers.

  • the old master branch is now moved to legacy-master branch.
  • the actual development repository's master and dev branch have been pushed to this repository.

From here onwards, we will continue updating this repo to be identical/inline both content and commit ID wise with the internal Cisco development repository, for 100% transparency.


Potential Impact

If you currently have a fork of this repository

  • Save your code changes, delete your fork, and re-fork.
  • Re-apply your changes on top of the new branches.
  • DO NOT try to merge legacy-master into master. The branch histories are un-related.

If you had PRs against this repository in the past

  • Your code changes should've been merged in already.

Having issues?

Clone this wiki locally