-
It would be useful to add a code coverage step to our workflow to ensure that we are not merging PRs that lack testing. There may be other options for this, but [this workflow](https://github.com/mar…
-
### Description
I am looking for ways to better verify my work before doing a pull request, to prevent unsuccessful use of the runners. I came across act, which has an extension for the github cli th…
-
After merging the GHAs imported from Josiah's repo to `master`, we will need to change all references to the remote actions and migrate to our local versions of them. At this point in time, we are onl…
-
We may use GitHub Actions.
Possible use cases:
- Building executables
- Signing executables
- Notification about new release
-
We can implement github workflows for the following things:
Auto comment on issue Closed and Opened
Auto comment on PR mergs
Auto comment on PR raises
Using this workflows makes you'r repo more …
-
> [!warning]
> ### Artifacts v3 brownouts
>Artifact actions v3 will be closing down by December 5, 2024. To raise awareness of the upcoming removal, we will temporarily fail jobs using v3 of actions…
-
Add testing and linting pipelines to verify PRs don't change intended behavior or diverge from code style guidance.
-
For a very long time I've been contemplating the idea of writing a package that lets you observe Github Actions logs without leaving Emacs.
Using `gh` (cmd-line tool) it is almost trivial to figure…
agzam updated
4 weeks ago
-
Artifact actions v3 will be deprecated by December 5, 2024. We currently have GitHub Actions workflows using v3 of actions/upload-artifact or actions/download-artifact. After this date using v3 of the…
-
We can implement github workflows for the following things:
Auto comment on issue Closed and Opened
Auto comment on PR mergs
Auto comment on PR raises
Using this workflows makes you'r repo more …