Add a dotnet format check workflow#216
Merged
TaoChenOSU merged 6 commits intomicrosoft:mainfrom Aug 21, 2023
Merged
Conversation
github-actions
Bot
added
the
github actions
crickman
previously approved these changes
Aug 20, 2023
glahaye
reviewed
Aug 21, 2023
glahaye
approved these changes
Aug 21, 2023
teamleader-dev
pushed a commit
to vlink-group/chat-copilot
that referenced
this pull request
Oct 7, 2024
### Motivation and Context <!-- Thank you for your contribution to the copilot-chat repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> There is currently no C# format check workflow for PRs. There is a workflow step in copilot-build-backend.yml that checks the format for the webapi, but that happens after the build step. There are two .Net projects in the repo (soon to be three). It's better to have a workflow that checks the format for the entire repo, instead of having multiple steps scattered around different workflows. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [Contribution Guidelines](https://github.com/microsoft/copilot-chat/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/copilot-chat/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄
kb0039
pushed a commit
to aaronba/chat-copilot
that referenced
this pull request
Jan 8, 2025
### Motivation and Context <!-- Thank you for your contribution to the copilot-chat repo! Please help reviewers and future users, providing the following information: 1. Why is this change required? 2. What problem does it solve? 3. What scenario does it contribute to? 4. If it fixes an open issue, please link to the issue here. --> There is currently no C# format check workflow for PRs. There is a workflow step in copilot-build-backend.yml that checks the format for the webapi, but that happens after the build step. There are two .Net projects in the repo (soon to be three). It's better to have a workflow that checks the format for the entire repo, instead of having multiple steps scattered around different workflows. ### Description <!-- Describe your changes, the overall approach, the underlying design. These notes will help understanding how your code works. Thanks! --> ### Contribution Checklist <!-- Before submitting this PR, please make sure: --> - [ ] The code builds clean without any errors or warnings - [ ] The PR follows the [Contribution Guidelines](https://github.com/microsoft/copilot-chat/blob/main/CONTRIBUTING.md) and the [pre-submission formatting script](https://github.com/microsoft/copilot-chat/blob/main/CONTRIBUTING.md#development-scripts) raises no violations - [ ] All unit tests pass, and I have added new tests where possible - [ ] I didn't break anyone 😄
jdtoombs
added a commit
to jdtoombs/chat-copilot
that referenced
this pull request
Apr 10, 2025
* extra validation for spec manager * slight fix * last fix * update
jdtoombs
pushed a commit
to jdtoombs/chat-copilot
that referenced
this pull request
Apr 10, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
There is currently no C# format check workflow for PRs. There is a workflow step in copilot-build-backend.yml that checks the format for the webapi, but that happens after the build step.
There are two .Net projects in the repo (soon to be three). It's better to have a workflow that checks the format for the entire repo, instead of having multiple steps scattered around different workflows.
Description
Contribution Checklist