Skip to content

Conversation

@rfiorella
Copy link
Contributor

No description provided.

@rfiorella rfiorella requested a review from ecoon November 18, 2025 20:22
@rfiorella rfiorella changed the title Reduce ci load by running only on PR or push to master [WIP] Reduce ci load by running only on PR or push to master Nov 18, 2025
@rfiorella
Copy link
Contributor Author

Current failure seems to be due to a GitHub outage, will revisit after fix is released

@rfiorella rfiorella changed the title [WIP] Reduce ci load by running only on PR or push to master Reduce ci load by running only on PR or push to master Nov 18, 2025
Copy link
Collaborator

@ecoon ecoon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved pending question...

working-directory: Docker
run: |
echo "ATS_BRANCH=$GITHUB_REF_NAME" >> $GITHUB_ENV
echo "ATS_BRANCH=${{ github.event.pull_request.head.ref }}" >> $GITHUB_ENV
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this work if it is not a PR, e.g. if push on master branch?

Copy link
Contributor Author

@rfiorella rfiorella Dec 1, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, I'm not sure but I would guess not

I'll split this into two jobs that run w/ on different conditions

@rfiorella rfiorella force-pushed the rich/reduce-ci-load branch from 096bdb4 to 6f270c5 Compare December 4, 2025 19:47
@rfiorella
Copy link
Contributor Author

@ecoon updated the logic you had a question about

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants