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

(maint) synced file(s) with chocolatey/.github #48

Merged
merged 4 commits into from
Jan 2, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
84 changes: 60 additions & 24 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -1,31 +1,67 @@
<!-- DO NOT MODIFY OR DELETE THIS TEMPLATE. IT IS USED IN AUTOMATION. -->
## Bug
<!--
BEFORE YOU CREATE A PULL REQUEST:

<!-- Search https://github.com/NuGet/Home/issues, and create one if you can't find a suitable issue. -->
<!-- Paste the full link, like https://github.com/nuget/home/issues/1000. GitHub will render is neatly. -->
Fixes:
Ensure you have read over [CONTRIBUTING.md](./CONTRIBUTING.md). We provide VERY defined guidance (as such, we strongly adhere to it).

Regression? Last working version:
A summary of our expectations:
- You are not submitting a pull request from your MASTER / MAIN branch.
- You are able to sign the Contributor License Agreement (CLA).
- YOUR GIT COMMIT MESSAGE FORMAT IS EXTREMELY IMPORTANT. We have a very defined expectation for this format and are sticklers about it. Really, READ the entire Contributing document. It will save you and us pain.
- Do not reformat code, it makes it hard to see what has changed. Leave the formatting to us.

## Description
<!-- Add details about the fix. Include any information that would help the maintainer review this change effective. -->
THANKS! We appreciate you reading the entire Contributing document and not just scanning through it.

## PR Checklist
Name your pull request appropriately: give it a sentence that reads well enough for anyone seeing this.

- [ ] PR has a meaningful title
- [ ] PR has a linked issue.
- [ ] Described changes
if you were explaining it to somebody else. This helps others to understand the reasons for the pull request and for it to be searchable in future.

- **Tests**
- [ ] Automated tests added
- **OR**
<!-- Describe why you haven't added automation. -->
- [ ] Test exception
- **OR**
- [ ] N/A <!-- Infrastructure, documentation etc. -->
Please do not remove any of the headings.
If a heading is not applicable then enter N/A: Why it's not applicable

- **Documentation**
<!-- Please link the PR/issue if appropriate -->
- [ ] Documentation PR or issue filled
- **OR**
- [ ] N/A
Make sure you have raised an issue for this pull request before continuing.

Please remove all comments before submitting.
-->

## Description Of Changes
<!-- Enter a description of the pull request changes -->

## Motivation and Context
<!-- Why is this change necessary and under what context is it being done -->

## Testing
<!-- How has this change been tested? If multiple different tests have been done please list them.
1. Tested this way
1. Tested that way
-->
### Operating Systems Testing
<!-- If this is a code change, list the operating systems this has been tested on
- Windows Server 2008R2
- Windows 8.1
...
-->

## Change Types Made
<!-- Tick the boxes for the type of changes that have been made -->

* [ ] Bug fix (non-breaking change).
* [ ] Feature / Enhancement (non-breaking change).
* [ ] Breaking change (fix or feature that could cause existing functionality to change).
* [ ] Documentation changes.
* [ ] PowerShell code changes.

## Change Checklist

* [ ] Requires a change to the documentation.
* [ ] Documentation has been updated.
* [ ] Tests to cover my changes, have been added.
* [ ] All new and existing tests passed?
* [ ] PowerShell code changes: PowerShell v2 compatibility checked?

## Related Issue
<!-- Make sure you have raised an issue for this pull request before
continuing. -->

Fixes #

<!-- PLEASE REMOVE ALL COMMENTS BEFORE SUBMITTING -->
24 changes: 24 additions & 0 deletions .github/workflows/label-sync.yml
AdmiringWorm marked this conversation as resolved.
Show resolved Hide resolved
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
name: Sync labels
on:
workflow_dispatch:
schedule:
# Run at the end of the day (most likely UTC)
- cron: "0 0 * * *"

jobs:
labels:
# We use ubuntu as the image, as it is typically faster and cheaper (on private repos).
runs-on: ubuntu-latest

steps:
# uncomment the uses line if additional configuration in the current
# repository is used.
#- uses: actions/[email protected]
- uses: EndBug/[email protected]
with:
config-file: |
https://raw.githubusercontent.com/chocolatey/.github/main/.github/labels.yml
request-token: ${{ secrets.SYNC_TOKEN }} # Used when getting the config files.
AdmiringWorm marked this conversation as resolved.
Show resolved Hide resolved
delete-other-labels: true # After initial run, and verification change this to true
dry-run: false
token: ${{ secrets.SYNC_TOKEN }} # Used when updating the labels on the repository.
7 changes: 6 additions & 1 deletion .templates/default/issue-note.sbn
Original file line number Diff line number Diff line change
@@ -1 +1,6 @@
- {{ issue.title }} - see [#{{ issue.number }}]({{ issue.html_url }}).
{{
if issue_label == "Bug" || issue_label == "Bug Fix" || issue_label == "Bug Fixes"
}}- Fix - {{ issue.title }} - see [#{{ issue.number }}]({{ issue.html_url }}).
{{ else
}}- {{ issue.title }} - see [#{{ issue.number }}]({{ issue.html_url }}).
{{ end -}}