Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG] Errors in github actions

Open
#393 2 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
git, github-actions
Domain
ci-cd

Research direction

Start with the failed GitHub Actions run linked in the issue and inspect the workflow configuration and repository secret or permission settings involved in fetching pull requests. Done means the reported pull-request workflow completes without the authentication error; access to repository settings or maintainer intervention appears necessary.

Written by the indexing model from the issue text.

Description

Is there an existing issue for this?
  • I have searched the existing issues
Current Behavior

Github actions fails i.e. https://github.com/nvim-flutter/flutter-tools.nvim/actions/runs/11200029728

Fetching the repository
  /usr/bin/git -c protocol.version=2 fetch --no-tags --prune --progress --no-recurse-submodules --depth=1 origin +47b8c363c6bca75a16d9f233071596b19d30fb60:refs/remotes/pull/392/merge
  Error: fatal: could not read Username for 'https://github.com/': terminal prompts disabled
Expected Behavior

Actions should not fail because of permission errors.
This may be because of an expired PAT. I see I do not have permission to change secrets, I do not see the organization/repo setting tab. @akinsho, could you grant me permission to change secrets?

Steps To Reproduce

Create PR, check actions.

Environment

No response

Anything else?

No response

Dominant language
Lua
Stars
1.4k
Forks
118
Avg merge
3h 16m
Merged PRs (30d)
20

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nvim-flutter/flutter-tools.nvim

All issues in nvim-flutter/flutter-tools.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.