Skip to content

Add backport workflow#813

Open
acroca wants to merge 4 commits intodapr:mainfrom
acroca:backport
Open

Add backport workflow#813
acroca wants to merge 4 commits intodapr:mainfrom
acroca:backport

Conversation

@acroca
Copy link
Copy Markdown
Member

@acroca acroca commented Mar 2, 2026

Signed-off-by: Albert Callarisa <albert@diagrid.io>
@acroca acroca requested review from a team as code owners March 2, 2026 14:28
@codecov
Copy link
Copy Markdown

codecov bot commented Mar 2, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 54.62%. Comparing base (9743c6a) to head (74ee8ac).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #813   +/-   ##
=======================================
  Coverage   54.62%   54.62%           
=======================================
  Files          51       51           
  Lines        3469     3469           
=======================================
  Hits         1895     1895           
  Misses       1434     1434           
  Partials      140      140           

☔ 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.

backport:
uses: dapr/.github/.github/workflows/backport.yaml@main
secrets:
dapr_bot_token: ${{ secrets.DAPR_BOT_TOKEN }}
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Just a thought, do we need to be using the DAPR_BOT_TOKEN for this or can we use the standard actions workflow secret?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

it needs to be the dapr_bot due to a security measure in github where PRs created from workflows don't trigger other actions, meaning the backport PR wouldn't have CI checks.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Ah right yes

Copy link
Copy Markdown
Member

@mikeee mikeee left a comment

Choose a reason for hiding this comment

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

I'm fine with the bot token for now but workflows should probably be using the finegrained repo token later

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