theforeman / theforeman/foremanctl
forge fails if you happen to have a PR checked out
Open
Nobody has claimed this yet.
development
- Dominant language
- Python
- Stars
- 27
- Forks
- 47
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 40
Description
I had a Katello PR checked out and ./forge deploy-dev failed with
TASK [git_repository : Clone repository] ****************************************************************************************************************************************************
fatal: [localhost]: FAILED! => {
"changed": false,
"cmd": "/bin/git reset --hard origin/38839_hg_cv_env --",
"rc": 128
}
STDERR:
fatal: Failed to resolve 'origin/38839_hg_cv_env' as a valid revision.
MSG:
Failed to checkout branch 38839_hg_cv_env
PLAY RECAP **********************************************************************************************************************************************************************************
localhost : ok=132 changed=26 unreachable=0 failed=1 skipped=11 rescued=0 ignored=0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the ./forge deploy-dev entry point and reproduce the failure while a Katello PR is checked out. Trace the git repository task using the reported reset command and determine the expected behavior; done means deploy-dev completes without failing on the existing checked-out PR.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, python
- Domain
- cli, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100