Skip to content

Commit 7fbce9a

Browse files
LeaDevelopLeaDevelop
authored
Merge branch 'chocolatey:master' into (#73)-made-for-automation-gets-content
2 parents ba016f9 + 8e289bd commit 7fbce9a

1,010 files changed

Lines changed: 24592 additions & 22844 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎.editorconfig‎

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,9 +1,13 @@
11
root = true
22

33
[*]
4-
end_of_line = lf
54
insert_final_newline = true
65

6+
[*.{md,mdx}]
7+
charset = utf-8
8+
end_of_line = lf
9+
trim_trailing_whitespace = false
10+
711
[*.{js,json,yml}]
812
charset = utf-8
913
indent_style = space

‎.gitattributes‎

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,8 @@
1+
* text=auto
2+
3+
*.mdx linguist-detectable eol=lf
4+
*.md linguist-detectable eol=lf
5+
16
/.yarn/** linguist-vendored
27
/.yarn/releases/* binary
38
/.yarn/plugins/**/* binary

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
1-
blank_issues_enabled: false
2-
contact_links:
3-
- name: Ask A Question
4-
url: https://github.com/chocolatey/docs/discussions
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: Ask A Question
4+
url: https://github.com/chocolatey/docs/discussions
55
about: Please ask and answer questions here.

‎.github/PULL_REQUEST_TEMPLATE.md‎

Lines changed: 59 additions & 57 deletions
Original file line numberDiff line numberDiff line change
@@ -1,57 +1,59 @@
1-
<!--
2-
BEFORE YOU CREATE A PULL REQUEST:
3-
4-
Ensure you have read over [CONTRIBUTING.md](./CONTRIBUTING.md). We provide VERY defined guidance (as such, we strongly adhere to it).
5-
6-
A summary of our expectations:
7-
- You are not submitting a pull request from your MASTER / MAIN branch.
8-
- 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.
9-
- Do not reformat code, it makes it hard to see what has changed. Leave the formatting to us.
10-
11-
THANKS! We appreciate you reading the entire Contributing document and not just scanning through it.
12-
13-
Name your issue appropriately: give it a sentence that reads well enough for anyone seeing this in release notes to know what the issue is.
14-
15-
When writing out the pull request details please ensure you are writing it as
16-
if you were explaining it to somebody else.
17-
Even if you will be working on and resolving the issue yourself.
18-
This helps others to understand the reasons for the pull request and for it to be searchable in future.
19-
20-
Please do not remove any of the headings.
21-
If a heading is not applicable then enter N/A: Why it's not applicable
22-
23-
Make sure you have raised an issue for this pull request before continuing.
24-
25-
Please remove all comments before submitting.
26-
-->
27-
28-
## Description Of Changes
29-
<!-- Enter a description of the pull request changes -->
30-
31-
## Motivation and Context
32-
<!-- Why is this change necessary and under what context is it being done -->
33-
34-
## Testing
35-
36-
* [ ] I have previewed these changes using the [Docker Container](https://github.com/chocolatey/docs/tree/master/.devcontainer) or another method before submitting this pull request.
37-
38-
## Change Types Made
39-
<!-- Tick the boxes for the type of changes that have been made -->
40-
41-
* [ ] Minor documentation fix (typos etc.).
42-
* [ ] Major documentation change (refactoring, reformatting or adding documentation to existing page).
43-
* [ ] New documentation page added.
44-
* [ ] The change I have made should have a video added, and I have raised an issue for this.
45-
* Issue #
46-
47-
## Change Checklist
48-
49-
* [ ] Requires a change to menu structure (top or left-hand side)/
50-
* [ ] Menu structure has been updated
51-
52-
## Related Issue
53-
<!-- Make sure you have raised an issue for this pull request before continuing. -->
54-
55-
Fixes #
56-
57-
<!-- PLEASE REMOVE ALL COMMENTS BEFORE SUBMITTING -->
1+
<!--
2+
BEFORE YOU CREATE A PULL REQUEST:
3+
4+
Ensure you have read over [CONTRIBUTING.md](./CONTRIBUTING.md). We provide VERY defined guidance (as such, we strongly adhere to it).
5+
6+
A summary of our expectations:
7+
- You are not submitting a pull request from your MASTER / MAIN branch.
8+
- 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.
9+
- Do not reformat code, it makes it hard to see what has changed. Leave the formatting to us.
10+
11+
THANKS! We appreciate you reading the entire Contributing document and not just scanning through it.
12+
13+
Name your issue appropriately: give it a sentence that reads well enough for anyone seeing this in release notes to know what the issue is.
14+
15+
When writing out the pull request details please ensure you are writing it as
16+
if you were explaining it to somebody else.
17+
Even if you will be working on and resolving the issue yourself.
18+
This helps others to understand the reasons for the pull request and for it to be searchable in future.
19+
20+
Please do not remove any of the headings.
21+
If a heading is not applicable then enter N/A: Why it's not applicable
22+
23+
Make sure you have raised an issue for this pull request before continuing.
24+
25+
Please remove all comments before submitting.
26+
-->
27+
28+
## Description Of Changes
29+
<!-- Enter a description of the pull request changes -->
30+
31+
## Motivation and Context
32+
<!-- Why is this change necessary and under what context is it being done -->
33+
34+
## Testing
35+
36+
* [ ] I have previewed these changes using the [Docker Container](https://github.com/chocolatey/docs/tree/master/.devcontainer) or another method before submitting this pull request.
37+
38+
## Change Types Made
39+
<!-- Tick the boxes for the type of changes that have been made -->
40+
41+
* [ ] Minor documentation fix (typos etc.).
42+
* [ ] Major documentation change (refactoring, reformatting or adding documentation to existing page).
43+
* [ ] New documentation page added.
44+
* [ ] The change I have made should have a video added, and I have raised an issue for this.
45+
* Issue #
46+
47+
## Change Checklist
48+
49+
* [ ] Requires a change to menu structure (top or left-hand side)/
50+
* [ ] Menu structure has been updated
51+
* [ ] Images added to the [img](https://github.com/chocolatey/img) repository?
52+
* [ ] PR -
53+
54+
## Related Issue
55+
<!-- Make sure you have raised an issue for this pull request before continuing. -->
56+
57+
Fixes #
58+
59+
<!-- PLEASE REMOVE ALL COMMENTS BEFORE SUBMITTING -->

‎.github/workflows/stale.yml‎

Lines changed: 56 additions & 49 deletions
Original file line numberDiff line numberDiff line change
@@ -1,49 +1,56 @@
1-
name: 'Stale Issue and PR Cleanup'
2-
on:
3-
workflow_dispatch:
4-
schedule:
5-
- cron: '0 4 * * *'
6-
7-
permissions:
8-
issues: write
9-
pull-requests: write
10-
11-
jobs:
12-
stale:
13-
runs-on: ubuntu-latest
14-
steps:
15-
- uses: actions/stale@v9
16-
id: stale
17-
with:
18-
days-before-stale: 30
19-
days-before-close: 14
20-
exempt-all-assignees: false
21-
exempt-draft-pr: true
22-
stale-issue-label: "Pending Closure"
23-
stale-pr-label: 'Pending Closure'
24-
only-labels: '0 - Waiting on User'
25-
close-issue-label: "No Response / Stale"
26-
close-pr-label: "No Response / Stale"
27-
exempt-issue-labels: 'Security / CVE,2 - Working,3 - Review'
28-
exempt-pr-labels: 'Security / CVE,2 - Working,3 - Review'
29-
labels-to-remove-when-unstale: '0 - Waiting on User,Pending closure'
30-
remove-stale-when-updated: true
31-
stale-issue-message: |
32-
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
33-
This issue will be closed in 14 days if it continues to be inactive.
34-
close-issue-message: |
35-
Dear contributor,
36-
37-
As this issue seems to have been inactive for quite some time now, it has been automatically closed.
38-
If you feel this is a valid issue, please feel free to re-open the issue if / when a pull request
39-
has been added.
40-
Thank you for your contribution.
41-
42-
close-pr-message: |
43-
Dear contributor,
44-
45-
As this PR seems to have been inactive for 30 days after changes / additional information
46-
was requested, it has been automatically closed.
47-
If you feel the changes are still valid, please re-open the PR once all changes or additional information
48-
that was requested has been added.
49-
Thank you for your contribution.
1+
name: 'Stale Issue and PR Cleanup'
2+
on:
3+
workflow_dispatch:
4+
schedule:
5+
- cron: '0 4 * * *'
6+
7+
permissions:
8+
issues: write
9+
pull-requests: write
10+
11+
jobs:
12+
stale:
13+
runs-on: ubuntu-latest
14+
steps:
15+
# Action GitHub repository: https://github.com/actions/stale
16+
- uses: actions/stale@v9
17+
id: stale
18+
with:
19+
days-before-stale: 30
20+
days-before-close: 14
21+
exempt-all-assignees: false
22+
exempt-draft-pr: true
23+
stale-issue-label: "Pending Closure"
24+
stale-pr-label: "Pending Closure"
25+
only-labels: "0 - Waiting on User"
26+
close-issue-label: "No Response / Stale"
27+
close-issue-reason: "not_planned"
28+
close-pr-label: "No Response / Stale"
29+
exempt-issue-labels: "Security,2 - Working,3 - Review"
30+
exempt-pr-labels: "Security,2 - Working,3 - Review"
31+
labels-to-remove-when-unstale: "0 - Waiting on User,Pending closure"
32+
remove-stale-when-updated: true
33+
stale-issue-message: |
34+
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
35+
This issue will be closed in 14 days if it continues to be inactive.
36+
close-issue-message: |
37+
Dear contributor,
38+
39+
As this issue seems to have been inactive for quite some time now, it has been automatically closed.
40+
If you feel this is a valid issue, please feel free to re-open the issue if / when a pull request
41+
has been added.
42+
43+
Thank you for your contribution.
44+
stale-pr-message: |
45+
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
46+
This pull request will be closed in 14 days if it continues to be inactive.
47+
close-pr-message: |
48+
Dear contributor,
49+
50+
As this PR seems to have been inactive for 30 days after changes / additional information
51+
was requested, it has been automatically closed.
52+
53+
If you feel the changes are still valid, please re-open the PR once all changes or additional information
54+
that was requested has been added.
55+
56+
Thank you for your contribution.

‎.gitignore‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -58,7 +58,7 @@ favicon.ico
5858
.astro
5959

6060
# playwright
61-
/src/tests/
61+
/playwright/global/
6262
/test-results/
6363
/playwright-report/
6464
/blob-report/

‎Dockerfile‎

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,8 @@
11
FROM node:lts
22
WORKDIR /app
33

4+
RUN git config --global --add safe.directory /app
5+
46
COPY package.json yarn.lock ./
57

68
COPY . .

0 commit comments

Comments
 (0)