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

Support neutral naming for Kibana default branch #97827

Closed
10 tasks done
tylersmalley opened this issue Apr 21, 2021 · 3 comments
Closed
10 tasks done

Support neutral naming for Kibana default branch #97827

tylersmalley opened this issue Apr 21, 2021 · 3 comments
Assignees
Labels
impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Operations Team label for Operations Team

Comments

@tylersmalley
Copy link
Contributor

tylersmalley commented Apr 21, 2021

As part of a larger neutral naming effort, we want to move from using master as the default branch name in GitHub to main. This involves a number of steps, which we intend to take incrementally to avoid too much development disruption:

  • Create main branch from master for kibana repository
  • Automate synchronization of commits from master to main
  • Update all CI jobs building master to instead build main
  • Update any automation/bots monitoring master branch to instead watch main
  • Update release manager to release from main branch
  • Update any developer documentation, guides, etc referencing master branch

When the tasks above are complete, the following will then need to be done.

Renaming a branch will:

  • Re-target any open pull requests
  • Update any draft releases based on the branch
  • Move any branch protection rules that explicitly reference the old name
  • Update the branch used to build GitHub Pages, if applicable
  • Show a notice to repository contributors, maintainers, and admins on the repository homepage with instructions to update local copies of the repository
  • Show a notice to contributors who git push to the old branch
  • Redirect web requests for the old branch name to the new branch name
  • Return a "Moved Permanently" response in API requests for the old branch name
@tylersmalley tylersmalley added the Team:Operations Team label for Operations Team label Apr 21, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-operations (Team:Operations)

@tylersmalley tylersmalley changed the title Use neutral naming for Git branchs Rename the default branch from master to main Apr 26, 2021
@tylersmalley tylersmalley self-assigned this Aug 23, 2021
tylersmalley pushed a commit to tylersmalley/kibana that referenced this issue Sep 1, 2021
tylersmalley pushed a commit to tylersmalley/kibana that referenced this issue Sep 1, 2021
tylersmalley pushed a commit to tylersmalley/kibana that referenced this issue Sep 1, 2021
tylersmalley pushed a commit that referenced this issue Sep 1, 2021
@tylersmalley tylersmalley changed the title Rename the default branch from master to main Support neutral naming for Kibana default branch Sep 1, 2021
@tylersmalley tylersmalley added 1 and removed 1 labels Oct 11, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:small Small Level of Effort labels Oct 25, 2021
@gtback
Copy link
Member

gtback commented Oct 29, 2021

I turned off Kibana link checking for the docs in elastic/docs#2270 while I figure out some of the ghosts in that code.

@tylersmalley
Copy link
Contributor Author

This has been completed

@exalate-issue-sync exalate-issue-sync bot added loe:medium Medium Level of Effort and removed loe:small Small Level of Effort labels Nov 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Operations Team label for Operations Team
Projects
None yet
Development

No branches or pull requests

3 participants