Chore: fix fast-forward workflow

[black7375]

Description

Related Issue

Summary by CodeRabbit

• Chores
  • Improved workflow reliability by updating how pull request commits are checked out during release processes. The workflow now uses the commit SHA directly for more precise and streamlined operations.

Additional context

Checklist

[changeset-bot]

⚠️ No Changeset found

Latest commit: a7add5b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The .github/workflows/fast-forward.yml workflow was updated to enhance how the release job checks out the code. A new output, head_sha, was added to the fast-forward job to capture the pull request's head commit SHA when the PR is merged into the main branch. The release job now uses this SHA directly for repository checkout, replacing the previous logic that relied on fetching the PR branch name through an additional API call. This streamlines the workflow by removing unnecessary steps and directly referencing the commit of interest.

Changes

File(s)	Change Summary
.github/workflows/fast-forward.yml	Added head_sha output to fast-forward job, removed branch name API call in release job, and updated checkout to use head_sha instead of branch name.

Sequence Diagram(s)

sequenceDiagram
    participant PR as Pull Request
    participant FF as fast-forward job
    participant REL as release job
    participant GH as GitHub API

    PR->>FF: Trigger workflow on PR merge to main
    FF->>GH: Fetch PR details via API
    FF->>FF: Extract head_sha from API response
    FF-->>REL: Output head_sha if PR merged to main
    REL->>GH: Checkout repository at head_sha

Loading

Possibly related PRs

• Fix: CI - Hard Reset at changeset versioning #118 #119: Also modifies the workflow to add an output for the PR's head commit SHA and uses it for checkout.
• Chore: Combine fast forward and release workflows again #69 #75: Improves integration between fast-forward and release jobs, also involving commit SHA outputs.
• Fix: CI - remove hard reset #118 #166: Changes handling of commit SHAs in the workflow, removing a similar output and related steps.

Suggested labels

config/build

Poem

A hop, a skip, a workflow tweak,
Now head_sha is what we seek!
No more branches, just a SHA—
For checkouts clean, hurrah hurrah!
The rabbit’s code now leaps ahead,
With simpler steps and bugs to shed.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3793ec2 and a7add5b.

📒 Files selected for processing (1)

• .github/workflows/fast-forward.yml (3 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Triggered from #191 by @​black7375.

Checking if we can fast forward main (3793ec2) to fix-fast-forward (5758a1d).

Target branch (main):

commit 3793ec261cf3fdf094c89eb856889479837a1fab (HEAD -> main, origin/main)
Author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Date:   Sat Apr 19 22:49:39 2025 +0000

    Chore: Version Packages

Pull request (fix-fast-forward):

commit 5758a1d51e1e55ae165c2d0a818c41a2f5e0f5fc (pull_request/fix-fast-forward)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 08:09:49 2025 +0900

    Chore: fix fast-forward workflow

Can't fast forward main (3793ec2) to fix-fast-forward (5758a1d). main (3793ec2) is not a direct ancestor of fix-fast-forward (5758a1d). Branches appear to have diverged at abaf21a:

* 5758a1d51e1e55ae165c2d0a818c41a2f5e0f5fc Chore: fix fast-forward workflow
| * 3793ec261cf3fdf094c89eb856889479837a1fab Chore: Version Packages
|/  
* abaf21a820070455e136ebcf3a48883e09ad2449 Chore: Update yarn to 4.9.1 and refactor CI

commit abaf21a820070455e136ebcf3a48883e09ad2449
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:46:37 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

Rebase locally, and then force push to fix-fast-forward.

[github-actions]

Triggered from #191 (comment) by @​black7375.

Trying to fast forward main (3793ec2) to fix-fast-forward (5758a1d).

Target branch (main):

commit 3793ec261cf3fdf094c89eb856889479837a1fab (HEAD -> main, origin/main)
Author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Date:   Sat Apr 19 22:49:39 2025 +0000

    Chore: Version Packages

Pull request (fix-fast-forward):

commit 5758a1d51e1e55ae165c2d0a818c41a2f5e0f5fc (pull_request/fix-fast-forward)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 08:09:49 2025 +0900

    Chore: fix fast-forward workflow

Can't fast forward main (3793ec2) to fix-fast-forward (5758a1d). main (3793ec2) is not a direct ancestor of fix-fast-forward (5758a1d). Branches appear to have diverged at abaf21a:

* 5758a1d51e1e55ae165c2d0a818c41a2f5e0f5fc Chore: fix fast-forward workflow
| * 3793ec261cf3fdf094c89eb856889479837a1fab Chore: Version Packages
|/  
* abaf21a820070455e136ebcf3a48883e09ad2449 Chore: Update yarn to 4.9.1 and refactor CI

commit abaf21a820070455e136ebcf3a48883e09ad2449
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 07:46:37 2025 +0900

    Chore: Update yarn to 4.9.1 and refactor CI

Rebase locally, and then force push to fix-fast-forward.

[black7375]

/rebase

[black7375]

/fast-forward

[github-actions]

Triggered from #191 (comment) by @​black7375.

Trying to fast forward main (3793ec2) to fix-fast-forward (a7add5b).

Target branch (main):

commit 3793ec261cf3fdf094c89eb856889479837a1fab (HEAD -> main, origin/main)
Author: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Date:   Sat Apr 19 22:49:39 2025 +0000

    Chore: Version Packages

Pull request (fix-fast-forward):

commit a7add5bdb90b417c35e33664e4cba1c0413b0ed0 (pull_request/fix-fast-forward)
Author: alstjr7375 <alstjr7375@daum.net>
Date:   Sun Apr 20 08:09:49 2025 +0900

    Chore: fix fast-forward workflow

Fast forwarding main (3793ec2) to fix-fast-forward (a7add5b).

$ git push origin a7add5bdb90b417c35e33664e4cba1c0413b0ed0:main
To https://github.com/mincho-js/mincho.git
   3793ec2..a7add5b  a7add5bdb90b417c35e33664e4cba1c0413b0ed0 -> main