-
It seems coveralls is not working here.
I'm not 100% sure how this is set up with the shared workflows: https://github.com/fastify/fastify-request-context/actions/runs/10941277501/job/30375549553#s…
-
**Describe the bug**
There are warnings in the current pre-release workflow that should be addressed:
- Package InFlight not supported.
- Package Glob: Use v9.0.0 or newer.
- VSCE should be in…
-
Hello,
this issue is somewhat related to #14625 but I'd like to suggest something slightly different.
Basically, I need global filter values to be resolved on a per-request basis, even if the `Db…
-
This is only required if we find the solution above requires the developer to remember or know the available list of actions and scopes.
#### Tasks:
- Research existing solutions for updating P…
-
We don't have user context yet, but once we do, this should be implemented. The user should have recent actions that they manually performed, and those should be listed on the dashboard.
-
**Describe the bug**
In GitHub workflows, we can access pull request data in some ways. We currently identify when it's accessed as `github.event.pull_request`.
https://github.com/ossf/scorecard/b…
-
the job id can not be determined if the action is part of a reusable workflow.
The problem seems to be that the actual job name is something like ` / `
-
## Context
User scoped variables are a new feature in st2. Currently, users can refer to an item in key value store using {{system.foo}} syntax. We want to support {{user.foo}}. The context of who t…
-
The current build stamp generation returned by !ping is from a time before git, and doesn't really work right for Git.
Ideally, we'd be able to expose the current commit hash in !ping, both when it…
-
## context
It would be nice to have consistent action inputs so this is more predictable.
Perhaps the default opinion can be kebab case and be configurable?
## options
### `kebab` case
…