radius-project / radius-project/samples

Commits in the PRs created by upmerge workflow should be signed

Open
#2,201 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug triaged
Dominant language
TypeScript
Stars
36
Forks
37
Avg merge
2d 23h
Merged PRs (30d)
12

Description

Bug information

Steps to reproduce (required)

Run upmerge workflow and see that the DCO in the PR created is false.

Observed behavior (required)

DCO fails

Image

Desired behavior (required)

DCO should pass by default.

Workaround (optional)

You can set the DCO to pass manually.

System information

rad Version (required)

edge

Operating system (required)

Additional context

AB#14753

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by running the upmerge workflow and inspecting the pull request it creates, including its commit signatures and DCO result. Trace the workflow configuration that creates those commits; done means newly created upmerge PRs pass DCO by default without manual intervention.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.