#github-actions (2024-03)
Discussions related to GitHub Actions
2024-03-01
2024-03-04
I wonder if they fixed it fully. Is it me or anyone else also seeing intermittent errors in GHA such as
An action could not be found at the URI
?
Github does provide the full cloudnative experience: always assume it will be broken, be happy if it works …
GitHub Actions: Larger Runners; Windows 11 Beta GitHub Actions: Larger Runners; Windows 11 Beta The post GitHub Actions: Larger Runners; Windows 11 Beta appeared first on The GitHub Blog.
Just learned about this: https://actions-cool.github.io/github-action-branding/
1
@Igor Rodionov
2024-03-05
2024-03-06
Actions Fine Grained Permissions Actions Fine Grained Permissions The post Actions Fine Grained Permissions appeared first on The GitHub Blog.
2024-03-07
GitHub Actions; All Actions will run on Node20 instead of Node16 by default GitHub Actions; All Actions will run on Node20 instead of Node16 by default The post GitHub Actions; All Actions will run on Node20 instead of Node16 by default appeared first on The GitHub Blog.
In other news, GitHub announced that 50% of the actions in the GitHub Marketplace will be deprecated on May 13th, 2024.
2
Trollface day was the day before yesterday …
2024-03-28
Actions Usage Metrics public beta Actions Usage Metrics public beta The post Actions Usage Metrics public beta appeared first on The GitHub Blog.
2024-03-29
I’m looking to automate my changelog/release/tags/release notes after whenever I merge a PR from renovatebot. Anyone here have recommendations on a FOSS to do what i described or something similar?
I’m currently digging through these and thinking about chaining something customer together:
https://github.com/marketplace?category=&type=actions&verification=&query=changelog
We have action for that, based on release-drafter
https://github.com/cloudposse/github-action-auto-release
Is there a way to get the labels added automatically? I’m looking at your code/nested actions and it seems like it might be missing functionality or specifically designed this way. I found a possible solution using: https://github.com/marketplace/actions/conventional-release-labels however, I am open to other ideas.
Shouldn’t patch be under ‘Bug fixes’? https://github.com/cloudposse/github-action-auto-release/blob/main/.github/configs/draft-release.yml#L27
I’m not sure. That’s a better question for @Igor Rodionov
I have a feeling this is an issue with the default draft-release.yml but was curious to know if you had any insights:
it looks like that’s a syntax error in your template, no?
Just did a diff between yours and ours and it’s identical from what i can tell:
https://github.com/cloudposse/github-action-auto-release/blob/main/.github/configs/draft-release.yml https://github.com/GlueOps/metacontroller-operator-waf/blob/main/.github/configs/draft-release.yml
Only difference is i have a header ontop that is commented out.
Had a few of these renovate bot PR’s that auto-release just didn’t like for some reason.
the syntax errors looks like it comes from the PR summary, which comes from renovate. we also use renovate and I’m not sure why it’s trying to render content in that summary
Thanks for the feedback. I’ll debug and share anything notable I find.