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.

Sign up for GitHub

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

Jump to bottom

Use main as primary branch #844

Open
lemeurherve opened this issue Mar 7, 2024 · 1 comment
Open

Use main as primary branch #844

lemeurherve opened this issue Mar 7, 2024 · 1 comment

Comments

@lemeurherve
Copy link
Member

lemeurherve commented Mar 7, 2024 •
edited
Loading

Suggestion

We should use main instead of master as primary branch.

This will need updating not only this repo but also all references to master in Jenkinsfile(s) and job on ci.jenkins.io, infra.ci.jenkins.io, release.ci.jenkins.io and trusted.ci.jenkins.io (not sure about cert.ci.jenkins.io), and changing settings of Jenkins instances around global shared pipeline library.

Links
@lemeurherve
Copy link
Member Author

Also be wary that this pipeline library is referenced in multiples repositories, a global search across them will be needed to ensure all references are updated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@lemeurherve