Skip to content

Explicitly pass GITHUB_TOKEN env to goreleaser action #1215

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

Merged
merged 3 commits into from
Jul 8, 2020

Conversation

SVilgelm
Copy link
Member

@SVilgelm SVilgelm commented Jul 6, 2020

Fix a failing release workflow

@boring-cyborg
Copy link

boring-cyborg bot commented Jul 6, 2020

Hey, thank you for opening your first Pull Request !

@CLAassistant
Copy link

CLAassistant commented Jul 6, 2020

CLA assistant check
All committers have signed the CLA.

@@ -23,3 +23,5 @@ jobs:
uses: goreleaser/goreleaser-action@v1
with:
args: release --rm-dist
env:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💯

Just curious on how to re-run, or one more release is required.

Copy link
Member Author

@SVilgelm SVilgelm Jul 6, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually it's impossible to re run this action because it triggers on a tag event:

on:
  push:
    tags:
      - v*

You can re-run failed actions, but they will use an old code.
Only one way to avoid a new release is run goreleaser manually

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

seems like only brew release was failing, I think we can re-run manually for brew only. /cc @golangci/team @golangci/core-team

args: release --rm-dist
env:
GITHUB_TOKEN: ${{ secrets.GOLANGCI_LINT_TOKEN }}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nits we can refer to env define in job level as well, something like ${{ env.GITHUB_TOKEN }}, but I think it's fine to use secrets.GOLANGCI_LINT_TOKEN here :)

@sayboras sayboras merged commit d287af0 into golangci:master Jul 8, 2020
@golangci-automator
Copy link

Hey, @SVilgelm — we just merged your PR to golangci-lint! 🔥🚀

golangci-lint is built by awesome people like you. Let us say “thanks”: we just invited you to join the GolangCI organization on GitHub.
This will add you to our team of maintainers. Accept the invite by visiting this link.

By joining the team, you’ll be able to label issues, review pull requests, and merge approved pull requests.
More information about contributing is here.

Thanks again!

@SVilgelm SVilgelm deleted the token-for-releaser branch July 9, 2020 15:29
@SVilgelm
Copy link
Member Author

SVilgelm commented Jul 9, 2020

@sayboras @golangci/team @golangci/core-team
Can we bump v1.28.2 to update the brew formulae? Or I can create a pr manually for tap repo

@sayboras
Copy link
Member

sayboras commented Jul 9, 2020

Thanks for your reminder. I just push new tag v1.28.2 to kick off the new release again. Sadly, it's still failing https://github.com/golangci/golangci-lint/runs/856010530?check_suite_focus=true.

Might need to wait for @golangci/core-team to help to verify GITHUB_TOKEN

@SVilgelm
Copy link
Member Author

SVilgelm commented Jul 9, 2020

yeah, I see, I checked the .goreleaser.yml and everything looks correct

@SVilgelm
Copy link
Member Author

SVilgelm commented Jul 9, 2020

@golangci/core-team Could you check please that the GITHUB_TOKEN has write permissions for the homebrew-tap repo?

@ldez ldez added the area: ci PR that update CI label Dec 7, 2020
@ldez ldez added this to the v1.28 milestone Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ci PR that update CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants