You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pull in upstream template changes
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Duplicate-pull-request detection to skip redundant CI runs.
* Validation workflow to ensure copier template uses a clean release
tag.
* CI now gates jobs conditionally and supports pull request events.
* **Chores**
* Devcontainer host requirements updated: 2 CPUs (runtime default 4GB;
template default 10GB).
* Updated devcontainer base image, VS Code extension pins, pnpm and
other tooling version bumps.
* Updated tag-on-merge publishing tooling.
* **Documentation**
* Strengthened Python tooling guidance.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Copy file name to clipboardExpand all lines: .devcontainer/Dockerfile
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
# base image tags available at https://mcr.microsoft.com/v2/devcontainers/universal/tags/list
2
2
# added the platform flag to override any local settings since this image is only compatible with linux/amd64. since this image is only x64 compatible, suppressing the hadolint rule
3
3
# hadolint ignore=DL3029
4
-
FROM --platform=linux/amd64 mcr.microsoft.com/devcontainers/universal:5.1.4-noble
4
+
FROM --platform=linux/amd64 mcr.microsoft.com/devcontainers/universal:5.1.5-noble
echo"It's likely the Dolt server has not yet been initialized to support beads, running that now"# TODO: figure out a better way to match this specific scenario than just a non-zero exit code...but beads still seems like in high flux right now so not sure what to tie it to
description: 'Check that will output a variable to allow you to skip duplicate runs. Example: If you have both push and pull_request triggers enabled and you dont want to run 2 jobs for the same commit if a PR is already open you can add this to your jobs to skip that extra execution.'
3
+
4
+
outputs:
5
+
should-run:
6
+
description: 'Flag that determines if this execution should run or not'
7
+
value: ${{ steps.check.outputs.should_run }}
8
+
9
+
runs:
10
+
using: composite
11
+
steps:
12
+
- name: Check if push has associated open PR
13
+
id: check
14
+
env:
15
+
GH_TOKEN: ${{ github.token }}
16
+
REF_NAME: ${{ github.ref_name }}
17
+
REPO_NAME: ${{ github.repository }}
18
+
EVENT_NAME: ${{ github.event_name }}
19
+
shell: bash
20
+
run: |
21
+
# For non-push events, always run
22
+
if [ "$EVENT_NAME" != "push" ]; then
23
+
echo "should_run=true" >> $GITHUB_OUTPUT
24
+
echo "Event is $EVENT_NAME, will run CI"
25
+
exit 0
26
+
fi
27
+
28
+
# For push events, check if there's an open PR for this branch
success_pattern="^(skipped|success)$" # these are the possibilities: https://docs.github.com/en/actions/reference/workflows-and-actions/contexts#needs-context
195
221
196
222
if [[ ! "${{ needs.get-values.result }}" =~ $success_pattern ]] ||
uses: nickkostov/github-tag-action@b3aa34b4ac9c7843ee609ba5d0b0a50b962647b9#v1.3.0 # a fork of https://github.com/mathieudutour/github-tag-action, which is still on Node 20
0 commit comments