Skip to content

Commit 468241b

Browse files
ImilerImiler
committed
adding required files for new ruleset
1 parent e403844 commit 468241b

File tree

4 files changed

+103
-52
lines changed

4 files changed

+103
-52
lines changed

‎.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 33 additions & 52 deletions
Original file line numberDiff line numberDiff line change
@@ -1,52 +1,33 @@
1-
<!--
2-
Thanks for submitting a Pull Request (PR) to this project. Your contribution to this project
3-
is greatly appreciated!
4-
5-
Please prefix the PR title with the resource name, e.g. 'ResourceName: My short description'.
6-
If this is a breaking change, then also prefix the PR title with 'BREAKING CHANGE:',
7-
e.g. 'BREAKING CHANGE: ResourceName: My short description'.
8-
9-
You may remove this comment block, and the other comment blocks, but please keep the headers
10-
and the task list.
11-
-->
12-
13-
#### Pull Request (PR) description
14-
15-
<!--
16-
Replace this comment block with a description of your PR. Also, make sure you have updated the
17-
CHANGELOG.md, see the task list below. An entry in the CHANGELOG.md is mandatory for all PRs.
18-
-->
19-
20-
#### This Pull Request (PR) fixes the following issues
21-
22-
<!--
23-
If this PR does not fix an open issue, replace this comment block with None. If this PR
24-
resolves one or more open issues, replace this comment block with a list of the issues using
25-
a GitHub closing keyword, e.g.:
26-
27-
- Fixes #123
28-
- Fixes #124
29-
-->
30-
31-
#### Task list
32-
33-
<!--
34-
To aid community reviewers in reviewing and merging your PR, please take the time to run
35-
through the below checklist and make sure your PR has everything updated as required.
36-
37-
Change to [x] for each task in the task list that applies to your PR. For those task that
38-
don't apply to you PR, leave those as is.
39-
-->
40-
41-
- [ ] Added an entry to the change log under the Unreleased section of the file CHANGELOG.md.
42-
Entry should say what was changed and how that affects users (if applicable), and
43-
reference the issue being resolved (if applicable).
44-
- [ ] Resource documentation added/updated in README.md.
45-
- [ ] Resource parameter descriptions added/updated in README.md, schema.mof and comment-based
46-
help.
47-
- [ ] Comment-based help added/updated.
48-
- [ ] Localization strings added/updated in all localization files as appropriate.
49-
- [ ] Examples appropriately added/updated.
50-
- [ ] Unit tests added/updated. See [DSC Community Testing Guidelines](https://dsccommunity.org/guidelines/testing-guidelines).
51-
- [ ] Integration tests added/updated (where possible). See [DSC Community Testing Guidelines](https://dsccommunity.org/guidelines/testing-guidelines).
52-
- [ ] New/changed code adheres to [DSC Community Style Guidelines](https://dsccommunity.org/styleguidelines).
1+
# Description
2+
3+
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
4+
5+
Fixes # (issue)
6+
7+
## Type of change
8+
9+
Please delete options that are not relevant.
10+
11+
- [ ] Bug fix (non-breaking change which fixes an issue)
12+
- [ ] New feature (non-breaking change which adds functionality)
13+
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
14+
- [ ] This change requires a documentation update
15+
16+
# How Has This Been Tested?
17+
18+
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
19+
20+
- [ ] Test A
21+
- [ ] Test B
22+
23+
24+
# Checklist:
25+
26+
- [ ] My code follows the style guidelines of this project
27+
- [ ] I have performed a self-review of my code
28+
- [ ] I have commented my code, particularly in hard-to-understand areas
29+
- [ ] I have made corresponding changes to the documentation
30+
- [ ] My changes generate no new warnings
31+
- [ ] I have added tests or screenshots that prove my fix is effective or that my feature works
32+
- [ ] Any dependent changes have been merged and published in downstream modules
33+

‎.github/labeler.yml

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
Feature:
2+
- head-branch: ['^feature', 'feature']
3+
Hotfix:
4+
- head-branch: ['^hotfix', 'hotfix']
5+
Documentation:
6+
- changed-files:
7+
- any-glob-to-any-file: '**/*.md'
8+
CICD:
9+
- changed-files:
10+
- any-glob-to-any-file: '.github/**'
11+
12+
typescript:
13+
- changed-files:
14+
- any-glob-to-any-file: '**/*.ts'
15+
css:
16+
- changed-files:
17+
- any-glob-to-any-file: '**/*.css'
18+
19+

‎.github/reviewers.yml

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
reviewers:
2+
defaults:
3+
- repository-owners
4+
- bbrauneck

‎.github/workflows/labelling.yaml

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
name: label PRs
2+
on:
3+
pull_request:
4+
branches: [dev, master]
5+
jobs:
6+
size-label:
7+
needs: pr-reviewer
8+
permissions:
9+
contents: read
10+
pull-requests: write
11+
runs-on: ubuntu-latest
12+
steps:
13+
- name: size-label
14+
uses: "pascalgn/size-label-action@v0.5.0"
15+
env:
16+
GITHUB_TOKEN: "${{ secrets.GITHUB_TOKEN }}"
17+
with:
18+
sizes: >
19+
{
20+
"0": "XS",
21+
"20": "S",
22+
"50": "M",
23+
"200": "L",
24+
"800": "XL",
25+
"2000": "XXL"
26+
}
27+
- name: general-labels
28+
uses: actions/labeler@v5
29+
with:
30+
sync-labels: true
31+
pr-reviewer:
32+
permissions:
33+
contents: read
34+
pull-requests: write
35+
runs-on: ubuntu-latest
36+
steps:
37+
- name: Checkout
38+
uses: actions/checkout@v3
39+
with:
40+
token: ${{ secrets.PAT || secrets.GITHUB_TOKEN }}
41+
fetch-depth: 0
42+
- name: Request review and assign
43+
uses: necojackarc/auto-request-review@v0.13.0
44+
with:
45+
token: ${{ secrets.GITHUB_TOKEN }}
46+
config: .github/reviewers.yml
47+
use_local: true

0 commit comments

Comments
 (0)