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
Comments
@sshnaidm Could you rename the master branch to the main branch, we want all of containers repos to fix this. |
@rhatdan sure, just got a lot on the plate recently |
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 |
Hi @sshnaidm, if you don't mind, can I work on this? It looks higher priority than others. |
@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. 🤝 |
Sure thanks! Then, I'll begin with grep master and identifying files required to be revised. |
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
Output of
ansible --version
:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Playbok you run with ansible (e.g. content of
playbook.yaml
):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
Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: