-
The container registry is filling up with tags from merged PR's. Is it possible to automatically delete these when the PR is merged?
 or macOS-15
-
## Pull Request report total
This report based on 9 last updated PRs. To learn more about the project and its configuration, please visit [Pull request analytics action](https://github.com/AlexSim9…
-
**Description**
There are no automated checks before merging a pull request yet. We should at least include format and lint checks.
**Links / References**
- See GitHub actions
**Tasks / Definitio…
-
## Pull Request report total
This report based on 1 last updated PRs. To learn more about the project and its configuration, please visit [Pull request analytics action](https://github.com/AlexSim9…
-
## Pull Request report total
This report based on 87 last updated PRs. To learn more about the project and its configuration, please visit [Pull request analytics action](https://github.com/AlexSim…
-
**Describe the bug**
When a GitHub Actions workflow runs on the `pull_request` event, `actions/checkout` by default does not check out the pull request branch itself, but merges it into the base bran…
-
Good PR's should
- No conflicts with the master branch
- Exclude binary files, .gitignore needs to be configured to handle this automatically
- References to the Issue tickets if any
- If po…
-
Somehow the coverage calculation for pull requests is off, see https://github.com/open-feature/python-sdk-contrib/pull/112 - I did not change the code, but I improved the coverage by some percent.
W…
-
### Current Behaviour
There is no auto label workflow for pull requests.
### Expected Behaviour
Newly opened PRs should be automatically labeled with `Review Queued` label of `#faff00` color.…