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

wolfibump doesn't work with different fork repo name #938

Open
TaylorBloom129 opened this issue Jun 4, 2024 · 0 comments
Open

wolfibump doesn't work with different fork repo name #938

TaylorBloom129 opened this issue Jun 4, 2024 · 0 comments
Labels
enhancement New feature or request needs-triage applied to all new customer/user issues. Removed after triage occurs.

Comments

@TaylorBloom129
Copy link

Description

Transferring issue over:

I was trying to use wolfibump with my wolfi-dev/os fork wlynch/wolfi-os, and ran into problems.

There's a lot of code that assumes the default forks name of a repositories.

Currently you get an error like:

2024/02/21 14:22:04 unable to create a pull request: will ignore this execution: branch already exists: while checking if repository is a fork of wolfi-dev/os: checking if repository is a fork: getting repository: GET https://api.github.com/repos/wlynch/os: 404 Not Found []

I tried wiring up a fork repo name flag, which then led me to the error:

2024/02/21 14:39:31 unable to create a pull request: will ignore this execution: branch already exists: a branch named main already exists in wlynch/wolfi-os

which doesn't quite make sense since we'd expect the main branch to exist on all forks.

I then tried setting the --wolfi-packages-repo-branch=wolfibump flag, but that failed because it assumes the same branch name for the fork checkout.

2024/02/21 14:43:15 failed to clone repository https://github.com/wolfi-dev/os.git into /var/folders/83/j7crs0zj5g9_nj3wb9hql9hh0000gn/T/wolfibump410073369: reference not found

Internal

@TaylorBloom129 TaylorBloom129 added enhancement New feature or request needs-triage applied to all new customer/user issues. Removed after triage occurs. labels Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-triage applied to all new customer/user issues. Removed after triage occurs.
Projects
None yet
Development

No branches or pull requests

1 participant