Skip to content

use github API to commit - which might make commits show up as verified?#20

Merged
Sajjon merged 2 commits intomainfrom
fix-sign-commits-attempt4
Jul 8, 2025
Merged

use github API to commit - which might make commits show up as verified?#20
Sajjon merged 2 commits intomainfrom
fix-sign-commits-attempt4

Conversation

@Sajjon
Copy link
Copy Markdown
Owner

@Sajjon Sajjon commented Jul 8, 2025

try to make commits made by CD show up as verified.

@Sajjon Sajjon requested a review from Copilot July 8, 2025 19:14

This comment was marked as outdated.

@codecov
Copy link
Copy Markdown

codecov bot commented Jul 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.90%. Comparing base (bceb3d8) to head (6fbe955).
Report is 2 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage   96.90%   96.90%           
=======================================
  Files          76       76           
  Lines        1650     1650           
=======================================
  Hits         1599     1599           
  Misses         51       51           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Sajjon Sajjon requested a review from Copilot July 8, 2025 19:25
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR updates the release workflow to create commits via the GitHub API, ensuring they appear as verified as part of the CD process.

  • Clarifies fetch-depth requirement for API operations
  • Replaces direct git commit/push with API-based commit and ref update
  • Adds JSON parsing and error handling around the API calls
Comments suppressed due to low confidence (2)

.github/workflows/release.yml:131

  • The workflow uses jq to parse JSON but does not install it. Consider adding a step to install jq before using it or switch to a parser available on the runner.
            NEW_SHA=$(echo "$COMMIT_RESPONSE" | jq -r '.sha')

.github/workflows/release.yml:106

  • [nitpick] This block of raw curl commands is lengthy and can be harder to maintain. You could simplify and maintain this logic using actions/github-script or the GitHub CLI (gh api).
            COMMIT_RESPONSE=$(curl -s -f -X POST \

@Sajjon Sajjon merged commit 606ac6b into main Jul 8, 2025
5 checks passed
@Sajjon Sajjon deleted the fix-sign-commits-attempt4 branch July 8, 2025 19:27
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