-
Notifications
You must be signed in to change notification settings - Fork 31
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
Failure on Gitea/Forgejo #117
Comments
Allow `nix flake update --commit-lock-file` to auto-commit the lock file after the update. This allows us to run `nix flake update` through CI without any external dependencies, such as DeterminateSystems' GitHub actions workflow, while also conforming to our commit messages standard. This decision was made particularly because of an issue with `update-flake-lock` [1] [1]: DeterminateSystems/update-flake-lock#117 Signed-off-by: Chinmay D. Pai <[email protected]>
I don't really believe that it's really related to this. I've forked this and changed the version to
So far I wasn't able to get enough more information on why this fails. This happens with both the original version and my modified version. I'll try to get more information as I learn how GitHub Actions are created. |
I was able to track down the issue! The issue is upstream at https://github.com/peter-evans/create-pull-request The action uses the wrong API URL for Forgejo/Gitea: The API endpoint is set to This issue is already reported upstream: peter-evans/create-pull-request#3569 If you want to get a working action until this gets fixed upstream and updated here you I've made a working workflow file: Note Don't forget to modify the file to your liking. It's made for my use so you should probably change some things. |
This Action fails with the following error on Forgejo (and I am guessing on Gitea as well):
As you can see, it fails in the last step while trying to create a pull request. I think that's because a dependency -
peter-evans/create-pull-request@v6
here - is hard coded to use GitHub and doesn't support Gitea/Forgejo. (See this issue on that project.)The text was updated successfully, but these errors were encountered: