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

Needs go generate tag inaccurate #579

Closed
CryptoMaxPlanck opened this issue Feb 21, 2023 · 0 comments
Closed

Needs go generate tag inaccurate #579

CryptoMaxPlanck opened this issue Feb 21, 2023 · 0 comments

Comments

@CryptoMaxPlanck
Copy link
Contributor

In PRs such #576 , PR's that might have some go changes, and revert them do not remove the go generate tag.

trajan0x added a commit that referenced this issue Sep 25, 2023
As #1397 & #579 pointed out if a module is changed and then unchanged, the needs-go-generate action is not removed (this is blocking #1382 rn). For this reason, this pr:

- consolidates actions for `include_deps`=true and `include_deps`=false. This will also help with #1390 by halving api requests by git-changes-action. Further work could be done here by consolidating goreleaser into `go.yml` the future 
- Remove unchanged module labels. This is honestly kind of a pain and could lead to api rate limiting issues. The way we're going to deal with this is by starting an action for each label, but only running it if the event is a pull request and [this condition](https://stackoverflow.com/a/59588725) is met. Once this is done we can also add this to the needs-go-generate check to reduce the number of api calls to remove a lebl further helping w/ #1390 


---------

Co-authored-by: Trajan0x <[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

2 participants