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

Please rename the master branch to the main branch. #256

Open
rhatdan opened this issue May 13, 2021 · 6 comments · May be fixed by #634
Open

Please rename the master branch to the main branch. #256

rhatdan opened this issue May 13, 2021 · 6 comments · May be fixed by #634

Comments

@rhatdan
Copy link
Member

rhatdan commented May 13, 2021

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

/kind feature

Description

Steps to reproduce the issue:

Describe the results you received:

Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Version of the containers.podman collection:
Either git commit if installed from git: git show --summary
Or version from ansible-galaxy if installed from galaxy: ansible-galaxy collection list | grep containers.podman

(paste your output here)

Output of ansible --version:

(paste your output here)

Output of podman version:

(paste your output here)

Output of podman info --debug:

(paste your output here)

Package info (e.g. output of rpm -q podman or apt list podman):

(paste your output here)

Playbok you run with ansible (e.g. content of playbook.yaml):

(paste your output here)

Command line and output of ansible run with high verbosity

Please NOTE: if you submit a bug about idempotency, run the playbook with --diff option, like:

ansible-playbook -i inventory --diff -vv playbook.yml

(paste your output here)

Additional environment details (AWS, VirtualBox, physical, etc.):

@rhatdan
Copy link
Member Author

rhatdan commented Jun 18, 2021

@sshnaidm Could you rename the master branch to the main branch, we want all of containers repos to fix this.

@sshnaidm
Copy link
Member

@rhatdan sure, just got a lot on the plate recently

@ssbarnea
Copy link
Contributor

Doing that rename is quite easy these days, GH did most of the things, even the git client knows about that. You only need to grep for master inside the repository after doing the rename to spot additional changes needed.

@nishipy
Copy link
Contributor

nishipy commented Aug 23, 2023

Hi @sshnaidm, if you don't mind, can I work on this? It looks higher priority than others.
https://github.com/github/renaming

@sshnaidm
Copy link
Member

@nishipy hey, I don't mind of course, but this requires my involvement as repo owner, not something others can do. So I'll ping you when I'm available and have some time and we can do it together. 🤝

@nishipy
Copy link
Contributor

nishipy commented Aug 23, 2023

Sure thanks! Then, I'll begin with grep master and identifying files required to be revised.

@nishipy nishipy linked a pull request Aug 27, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants