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

docs release-process: use GH_USERNAME as a placeholder #367

Merged
merged 1 commit into from Feb 12, 2024

Conversation

gotmax23
Copy link
Contributor

At least on my system, the UNIX username is different than my Github
username. Let's change this var name accordingly so it can be more
easily copy-pasted.

At least on my system, the UNIX username is different than my Github
username. Let's change this var name accordingly so it can be more
easily copy-pasted.
@webknjaz
Copy link
Member

Fair, I have a different OS login too, though I also tend to fork repos adding the upstream org as a prefix. That's another corner case that's not evident. Does this doc really need to include every quirk? All such things are pretty much person-dependent. I'd say that the doc should describe the process that works for the majority, and the power users can figure it out.
Another improvement is automating these commands. It's not always possible to guess the right remote, but there could be a config with a mapping, like cherry-picker has.

@ssbarnea ssbarnea merged commit 05eb58b into ansible-community:main Feb 12, 2024
3 checks passed
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 this pull request may close these issues.

None yet

4 participants