[Salesforce Migration] Warning

[cloudybot]

Salesforce is in the process of migrating all repositories from github.com/SalesforceEng to github.com/salesforce. As a part of this migration, this repository is slated to be moved as well. To request an exception or for any concerns contact @SalesforceEng/osscore or email osscore@salesforce.com. There is no set date for the migration yet. For details on how GitHub repository transfers work, see here. Posted at 2016-08-23 22:45:38 PST.

[anish]

@saaja-sfdc Tom, Argus and Ian's project are our main concerns here. No issues on your side ?

[saaja-sfdc]

@anish I don't know because the risks haven't been expressed. What issues should I be concerned with? Will this break our travis-ci, codecov & coverity integrations? etc.. I'm not sure how to quantify the impact of the migration. I'm sure there will be work as a result of it. Either way, I think it's the right thing to do, so we'll just deal with whatever effects there are.

[anish]

@saaja-sfdc Should be quite painless. Since we're using github's repository transfers, all git remotes will be correctly redirected. From the documentation :

• If the transferred repository is a fork, then it remains associated with the upstream repository.
• If the transferred repository contains a GitHub Pages site, then links to the Git repository on the Web and through Git activity are redirected. However, we don't redirect GitHub Pages associated with the repository.
• If the transferred repository contains webhooks, services, or deploy keys, they will remain associated after the transfer is complete.
• If the transferred repository has any forks, then those forks will remain associated with the repository after the transfer is complete.
• All Git information about commits, including contributions, are preserved, unless Git history has been rewritten using git rebase.
• All of the issues and pull requests remain intact when transferring a repository.
• All links to the previous repository location are automatically redirected to the new location. When you use git clone, git fetch, or git push on a transferred repository, these commands will redirect to the new repository location or URL.

[anish]

I believe the only exception is teams, which need to be recreated (working on scripting this)

[saaja-sfdc]

Yea, I went through the repo transfer doc as well. Sounds magical. Hopefully it works as advertised. /fingerscrossed.

If teams are the only thing we have to recreate, we'll be in good shape.

[anish]

@kgowdru

[anish]

Barring people who haven't accepted yet, your teams have been recreated at /salesforce, just a matter of the actual migration now.

[anish]

Migration set for 7th November

[anish]

@saaja-sfdc @kgowdru Will do this at 11.30 PST if there are no more blockers on your side

[anish]

Migrated