Skip to content

Catch problems early on if --github-user is not specified for --new-pr & co#3644

Merged
boegel merged 5 commits intoeasybuilders:developfrom
ocaisa:github_user
Apr 10, 2021
Merged

Catch problems early on if --github-user is not specified for --new-pr & co#3644
boegel merged 5 commits intoeasybuilders:developfrom
ocaisa:github_user

Conversation

@ocaisa
Copy link
Copy Markdown
Member

@ocaisa ocaisa commented Apr 9, 2021

Fixes #3642 but probably could error earlier for the case of --new-pr rather than waste time cloning the repo

Comment thread easybuild/tools/github.py Outdated
@boegel boegel added the bug fix label Apr 10, 2021
@boegel boegel added this to the next release (4.3.5?) milestone Apr 10, 2021
…figs_pr_common helper function + require that target_account is not None in setup_repo_from and push_branch_to_github
@boegel boegel changed the title Catch problems if no github user specified Catch problems early on if no github user specified for --new-pr & co Apr 10, 2021
@boegel boegel changed the title Catch problems early on if no github user specified for --new-pr & co Catch problems early on if --github-user is not specified for --new-pr & co Apr 10, 2021
ocaisa added 2 commits April 10, 2021 12:17
make sure that --github-org or --github-user is specified in _easyconfigs_pr_common helper function + require that target_account is not None in setup_repo_from and push_branch_to_github
@boegel boegel merged commit 523b5cf into easybuilders:develop Apr 10, 2021
@ocaisa ocaisa deleted the github_user branch April 10, 2021 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

--new-pr does not check for valid GitHub user name

2 participants