Skip to content

Conversation

@prasad-sawantdesai
Copy link
Collaborator

@maarten-ic
Copy link
Collaborator

Hmm, not sure if this is the right approach. Now it looks as if no CI has run at all:
image

Or is that just a quirk of CI across forks? #20 also doesn't indicate whether CI checks are successful, while #25 does have it (but there the CI checks are run twice 🙂)

@prasad-sawantdesai
Copy link
Collaborator Author

I see, Lets see if this works, e75ed7a09231233e62ab4885fd541d217b64bb17

For similar case, I found below, I mean, check the name of the branch inside jobs..
https://github.com/orgs/community/discussions/57827

Copy link
Collaborator

@maarten-ic maarten-ic left a comment

Choose a reason for hiding this comment

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

Great! We now have the CI report in the PR summary overview, and all jobs only ran once 💯

@olivhoenen olivhoenen merged commit 062266a into iterorganization:develop Mar 18, 2025
9 checks passed
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