-
-
Notifications
You must be signed in to change notification settings - Fork 929
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
Provide repository info to gh
command in GitHub action
#7491
Conversation
This fixes the following error in the GitHub action: ``` failed to run git: fatal: not a git repository (or any of the parent directories): .git ``` https://github.com/stylelint/stylelint/actions/runs/7609612527/job/20721207993#step:2:19 The failure reason is that the `gh` command tries reading the `.git` repository. This change provides the repository info through an environment variable supported by `gh`. (see also https://cli.github.com/manual/gh_help_environment)
|
Oops. ![]() https://github.com/stylelint/stylelint/actions/runs/7609859353/job/20721956481#step:2:16 |
cb960f7 works now! 🎉 Example: #6362 (comment) |
I can confirm that; my notification center was full of these. |
Ya, me too. 😅 |
@ybiquitous |
@Mouvedia Ah, great catch! It's due to $ gh issue list -h
...
-L, --limit int Maximum number of issues to fetch (default 30)
... We need to increase the limit. I'll open one more PR soon. 👍🏼 |
Otherwise, one more PR is unneeded since we can trigger the action again to reduce the rest. $ gh issue list --search "is:open updated:<${one_month_ago} label:\"status: ready to implement\""
Showing 24 of 24 issues in stylelint/stylelint that match your search
... |
We are gonna bother so many ppl. I am feeling regretful to have found out. |
Done! ✅
Confirmed locally: $ gh issue list --search "is:open updated:<${one_month_ago} label:\"status: ready to implement\""
no issues match your search in stylelint/stylelint |
Exactly. 😓 |
|
This fixes the following error in the GitHub action:
https://github.com/stylelint/stylelint/actions/runs/7609612527/job/20721207993#step:2:19
The failure reason is that the
gh
command tries reading the.git
repository.This change provides the repository info through an environment variable supported by
gh
.(see also https://cli.github.com/manual/gh_help_environment)
Follow-up to PR #7486
By the way, if cli/cli#3556 was realized, this PR would be no longer needed.