Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update SDK-PR-guide.md to include inter-branch codeflow #47420

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

marcpopMSFT
Copy link
Member

  • Include links to the flow yml, config, and actions.
  • Include comment about failed actions and PR updates
  • Include 0 size PRs
  • Include merge commit

@Copilot Copilot bot review requested due to automatic review settings March 10, 2025 18:56
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Request triage from a team member labels Mar 10, 2025
Copy link
Contributor

@Copilot 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.

PR Overview

This PR updates the SDK PR guide to include instructions and links related to the inter-branch codeflow process.

  • Introduces a new "Inter-branch codeflow" section with links to configuration files.
  • Provides guidelines on handling failed workflow automation and PR merge methods.
  • Explains considerations for PRs with zero changes due to automated version bumps.

Reviewed Changes

File Description
documentation/project-docs/SDK-PR-guide.md Adds new documentation for inter-branch codeflow and merge practices

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

marcpopMSFT and others added 3 commits March 10, 2025 11:58
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
@baronfel
Copy link
Member

image

The rich preview isn't showing the 'important' note well enough, so here's what it looks like. Maybe a warning instead?

### Reviewing and merging inter-branch codeflow
Generally we will check the commit list and scan the changes for anything out of the ordinary. We take a special look for any conflict merges that were done in getting the PR building.
> [!Important]
> Make sure to create a merge commit. Do not squash. If you squash, the next inter-branch PR will list all of the same commits.
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
> Make sure to create a merge commit. Do not squash. If you squash, the next inter-branch PR will list all of the same commits.
> Make sure to create a merge commit. *Do not squash*. If you squash, the next inter-branch PR will list all of the same commits.

Just in case (?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants