Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update FDC3 master branch to main #579

Closed
6 tasks done
Julia-Ritter opened this issue Feb 3, 2022 · 4 comments
Closed
6 tasks done

Update FDC3 master branch to main #579

Julia-Ritter opened this issue Feb 3, 2022 · 4 comments
Assignees
Labels

Comments

@Julia-Ritter
Copy link
Contributor

Julia-Ritter commented Feb 3, 2022

Description:

The FDC3 team would like to rename the repo master branch to main.

Items

  • Agree on this list of tasks as the plan to move forward
  • Prepare a PR with name replacement across the entire codebase; this includes, but is not limited, to links and GitHub actions; this is a good start - https://github.com/search?q=repo%3Afinos%2FFDC3%20master&type=code
  • Choose a target date for merging
  • Notify community
  • Rename the branch and merge the PR
  • Post-migration check for broken links
@Julia-Ritter Julia-Ritter added the docs Documentation label Feb 3, 2022
@kriswest kriswest added this to the post-2.0 tasks milestone May 17, 2022
@maoo maoo changed the title Repo change: FINOS and FDC3 to update FDC3 master branch to main Update FDC3 master branch to main Feb 19, 2024
@maoo
Copy link
Member

maoo commented Feb 19, 2024

@kriswest - happy to support this! I took the freedom to rewrite title and description of the issue; WDYT?

cc @robmoffat @TheJuanAndOnly99

@kriswest
Copy link
Contributor

LGTM, that search is revealing more links than I thought there were, so good start!

I'd include doing a post-migration check for broken links at the end of the steps. I think docusaurus does its own link checking and will report build errors if they're found, but we may also want to run a 3rd party tool - neither will find anything until after the branch rename of course.

@TheJuanAndOnly99
Copy link
Member

PR is ready #1161.

@kriswest
Copy link
Contributor

Merged and completed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants