Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: tailcallhq/forgecode
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Choose a base ref
...
head repository: tailcallhq/forgecode
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: bounty-scripts-fixes
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 15 commits
  • 17 files changed
  • 2 contributors

Commits on Mar 23, 2026

  1. Configuration menu
    Copy the full SHA
    c3ff4e4 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    3843fcb View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    d5aabc3 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    7058c62 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    58852e8 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    89040c0 View commit details
    Browse the repository at this point in the history
  7. Configuration menu
    Copy the full SHA
    be7bb47 View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    9f5ce81 View commit details
    Browse the repository at this point in the history
  9. Configuration menu
    Copy the full SHA
    21c983f View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    c277389 View commit details
    Browse the repository at this point in the history
  11. Configuration menu
    Copy the full SHA
    dec3bda View commit details
    Browse the repository at this point in the history
  12. Configuration menu
    Copy the full SHA
    add9d2c View commit details
    Browse the repository at this point in the history
  13. Configuration menu
    Copy the full SHA
    98a69b9 View commit details
    Browse the repository at this point in the history
  14. fix(bounty): add if conditions to sync-issue and sync-pr jobs

    Both jobs now guard against running on the wrong event type:
    - sync-issue: only runs on 'issues' events
    - sync-pr: only runs on 'pull_request' or 'pull_request_target' events
    
    Without these guards, sync-pr would execute on issues events where
    github.event.pull_request.number is null/undefined, causing failures.
    Similarly, sync-issue would run on PR events with a null issue number.
    
    Co-Authored-By: ForgeCode <noreply@forgecode.dev>
    tusharmath and forge-code-agent committed Mar 23, 2026
    Configuration menu
    Copy the full SHA
    cdf7d11 View commit details
    Browse the repository at this point in the history
  15. fix(bounty): pass --execute flag to sync scripts in CI

    Both sync-issue.ts and sync-pr.ts default to dry-run mode (plan only)
    unless --execute is passed. The CI workflow was calling them without
    this flag, so no label changes were ever applied — the scripts would
    just print a plan and exit successfully.
    
    This caused the bounty label added to issue #2630 to never be synced.
    
    Co-Authored-By: ForgeCode <noreply@forgecode.dev>
    tusharmath and forge-code-agent committed Mar 23, 2026
    Configuration menu
    Copy the full SHA
    e3406db View commit details
    Browse the repository at this point in the history
Loading