Skip to content

Correctly check out the repository so validate-commits works for forks#162

Closed
RealOrangeOne wants to merge 1 commit into
kraken-tech:mainfrom
RealOrangeOne:validate-commits-on-forks
Closed

Correctly check out the repository so validate-commits works for forks#162
RealOrangeOne wants to merge 1 commit into
kraken-tech:mainfrom
RealOrangeOne:validate-commits-on-forks

Conversation

@RealOrangeOne

Copy link
Copy Markdown
Contributor

The previous checkout mechanism only worked for branches on the source repository, not for forks.

This change checks out the source repository, and adds the fork as another remote which is then checked out. This keeps main as the upstream, and keeps the fork branch.

This may do strange things if the branch isn't up-to-date with main, but there may not be a simple way around that (outside of validate-commits itself).

@RealOrangeOne
RealOrangeOne requested a review from a team as a code owner May 20, 2026 16:31
@meshy

meshy commented Jun 1, 2026

Copy link
Copy Markdown
Collaborator

Thank you for bringing this to our attention.

We've taking another approach to fixing this in #167. Please let us know if that doesn't fix it!

@meshy meshy closed this Jun 1, 2026
@RealOrangeOne
RealOrangeOne deleted the validate-commits-on-forks branch June 9, 2026 11:18
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.

2 participants