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

Failure on Gitea/Forgejo #117

Open
ketan-vijayvargiya opened this issue Jun 13, 2024 · 0 comments
Open

Failure on Gitea/Forgejo #117

ketan-vijayvargiya opened this issue Jun 13, 2024 · 0 comments

Comments

@ketan-vijayvargiya
Copy link

This Action fails with the following error on Forgejo (and I am guessing on Gitea as well):

Persisted git credentials restored
[command]/usr/bin/git config --global --unset safe.directory /workspace/ketan/nix-config
  ❓  ::endgroup::
::endgroup::
  ❌  Failure - Main Create PR
exitcode '1': failure
expression '${{ steps.create-pr.outputs.pull-request-number }}' rewritten to 'format('{0}', steps.create-pr.outputs.pull-request-number)'
evaluating expression 'format('{0}', steps.create-pr.outputs.pull-request-number)'
expression 'format('{0}', steps.create-pr.outputs.pull-request-number)' evaluated to '%!t(string=)'
  ⚙  ::set-output:: pull-request-number=
expression '${{ steps.create-pr.outputs.pull-request-operation }}' rewritten to 'format('{0}', steps.create-pr.outputs.pull-request-operation)'
evaluating expression 'format('{0}', steps.create-pr.outputs.pull-request-operation)'
expression 'format('{0}', steps.create-pr.outputs.pull-request-operation)' evaluated to '%!t(string=)'
  ⚙  ::set-output:: pull-request-operation=
  ❌  Failure - Main Update flake.lock
exitcode '1': failure

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.)

Thunderbottom added a commit to Thunderbottom/flakes that referenced this issue Oct 28, 2024
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]>
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

No branches or pull requests

1 participant