Skip to content

Commit 98d054f

Browse files
seanbuddseanbudd
authored
Merge 0296486 into 9ea2566 
2 parents 9ea2566 + 0296486 commit 98d054f

757 files changed

Lines changed: 487289 additions & 487287 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.

‎.coderabbit.yml‎

Lines changed: 53 additions & 53 deletions
Original file line numberDiff line numberDiff line change
@@ -1,53 +1,53 @@
1-
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
2-
# https://docs.coderabbit.ai/guides/configure-coderabbit/
3-
4-
language: "en-US"
5-
early_access: true
6-
reviews:
7-
profile: "chill"
8-
high_level_summary: true
9-
request_changes_workflow: false
10-
review_status: false
11-
collapse_walkthrough: false
12-
poem: false
13-
auto_review:
14-
enabled: true
15-
auto_incremental_review: false
16-
drafts: false
17-
base_branches:
18-
- master
19-
- beta
20-
- rc
21-
path_instructions:
22-
- path: "**/*"
23-
instructions: "
24-
Focus on code smells, logic errors, edge cases, missing test cases, security flaws and serious issues.
25-
Avoid commenting on minor issues such as linting, formatting and style issues.
26-
This project uses tabs instead of spaces, do not suggest usage of spaces over tabs.
27-
Are there any 'red flags' in this code that might warrant closer investigation from a security standpoint?
28-
Explain what makes them suspicious.
29-
"
30-
- path: "**/*.py"
31-
instructions: "
32-
_, pgettext, ngettext, and ngettext are defined globally, errors for this being undefined can be ignored.
33-
"
34-
- path: "**/*.md"
35-
instructions: "
36-
Focus on grammar, spelling, and punctuation.
37-
Also consider readability and clarity of contents.
38-
Ensure that changes follow the style of one sentence per line, suggest changes if this is not met.
39-
"
40-
tools:
41-
github-checks:
42-
enabled: true
43-
ruff:
44-
# Should become true if we switch linters,
45-
# right now linting is done by a flake8 check (#14817).
46-
enabled: false
47-
markdownlint:
48-
# We use custom markdown syntax such as {#Anchor} for anchors.
49-
# This is not supported by markdownlint.
50-
# In future we plan to introduce markdownlint directly with custom rules. (#16453)
51-
enabled: false
52-
chat:
53-
auto_reply: true
1+
# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json
2+
# https://docs.coderabbit.ai/guides/configure-coderabbit/
3+
4+
language: "en-US"
5+
early_access: true
6+
reviews:
7+
profile: "chill"
8+
high_level_summary: true
9+
request_changes_workflow: false
10+
review_status: false
11+
collapse_walkthrough: false
12+
poem: false
13+
auto_review:
14+
enabled: true
15+
auto_incremental_review: false
16+
drafts: false
17+
base_branches:
18+
- master
19+
- beta
20+
- rc
21+
path_instructions:
22+
- path: "**/*"
23+
instructions: "
24+
Focus on code smells, logic errors, edge cases, missing test cases, security flaws and serious issues.
25+
Avoid commenting on minor issues such as linting, formatting and style issues.
26+
This project uses tabs instead of spaces, do not suggest usage of spaces over tabs.
27+
Are there any 'red flags' in this code that might warrant closer investigation from a security standpoint?
28+
Explain what makes them suspicious.
29+
"
30+
- path: "**/*.py"
31+
instructions: "
32+
_, pgettext, ngettext, and ngettext are defined globally, errors for this being undefined can be ignored.
33+
"
34+
- path: "**/*.md"
35+
instructions: "
36+
Focus on grammar, spelling, and punctuation.
37+
Also consider readability and clarity of contents.
38+
Ensure that changes follow the style of one sentence per line, suggest changes if this is not met.
39+
"
40+
tools:
41+
github-checks:
42+
enabled: true
43+
ruff:
44+
# Should become true if we switch linters,
45+
# right now linting is done by a flake8 check (#14817).
46+
enabled: false
47+
markdownlint:
48+
# We use custom markdown syntax such as {#Anchor} for anchors.
49+
# This is not supported by markdownlint.
50+
# In future we plan to introduce markdownlint directly with custom rules. (#16453)
51+
enabled: false
52+
chat:
53+
auto_reply: true

‎.git-blame-ignore-revs‎

Lines changed: 10 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,10 @@
1-
# Documentation: https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt
2-
# Usage: git config --local blame.ignoreRevsFile .git-blame-ignore-revs
3-
4-
# Normalize line endings in t2t files
5-
e6a639bfe237ff7f98c4cbec2094a34ac4b879db
6-
# Migrate t2t to markdown
7-
884c75fe73accbc36bf81260827f4d21c7f40074
8-
7afafc698a0c5e6689701f024764ca525acf50af
1+
# Documentation: https://git-scm.com/docs/git-blame#Documentation/git-blame.txt---ignore-revs-fileltfilegt
2+
# Usage: git config --local blame.ignoreRevsFile .git-blame-ignore-revs
3+
4+
# Normalize line endings in t2t files
5+
e6a639bfe237ff7f98c4cbec2094a34ac4b879db
6+
# Migrate t2t to markdown
7+
884c75fe73accbc36bf81260827f4d21c7f40074
8+
7afafc698a0c5e6689701f024764ca525acf50af
9+
# Normalize all line endings
10+
8fb8ffcaba3950b1e4ca7b58e165267fc5369eb9

‎.github/CODEOWNERS‎

Lines changed: 56 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -1,56 +1,56 @@
1-
# This is a comment.
2-
# Each line is a file pattern followed by one or more owners.
3-
4-
# These owners will be the default owners for everything in
5-
# the repo. Unless a later match takes precedence,
6-
# @global-owner1 and @global-owner2 will be requested for
7-
# review when someone opens a pull request.
8-
# * @global-owner1 @global-owner2
9-
10-
# Order is important; the last matching pattern takes the most
11-
# precedence. When someone opens a pull request that only
12-
# modifies JS files, only @js-owner and not the global
13-
# owner(s) will be requested for a review.
14-
# *.js @js-owner
15-
16-
# You can also use email addresses if you prefer. They'll be
17-
# used to look up users just like we do for commit author
18-
# emails.
19-
# *.go docs@example.com
20-
21-
# In this example, @doctocat owns any files in the build/logs
22-
# directory at the root of the repository and any of its
23-
# subdirectories.
24-
# /build/logs/ @doctocat
25-
26-
# The `docs/*` pattern will match files like
27-
# `docs/getting-started.md` but not further nested files like
28-
# `docs/build-app/troubleshooting.md`.
29-
# docs/* docs@example.com
30-
31-
# In this example, @octocat owns any file in an apps directory
32-
# anywhere in your repository.
33-
# apps/ @octocat
34-
35-
# In this example, @doctocat owns any file in the `/docs`
36-
# directory in the root of your repository and any of its
37-
# subdirectories.
38-
# /docs/ @doctocat
39-
40-
# Start of NVDA config
41-
42-
# By default auto request review from NV Access developer team.
43-
* @nvaccess/developers
44-
45-
# For changes to the userGuide auto request review from userDocs team
46-
/user_docs/en/userGuide.md @nvaccess/userDocs
47-
/projectDocs/dev/userGuideStandards.md @nvaccess/userDocs
48-
49-
# For various project documentation, require appropriate teams
50-
/projectDocs/community/ @nvaccess/userDocs
51-
/projectDocs/testing/ @nvaccess/userDocs @nvaccess/developers
52-
/projectDocs/issues/ @nvaccess/userDocs @nvaccess/developers
53-
/readme.md @nvaccess/userDocs @nvaccess/developers
54-
security.md @nvaccess/userDocs @nvaccess/developers
55-
CODE_OF_CONDUCT.md @nvaccess/userDocs @nvaccess/developers
56-
.github/CONTRIBUTING.md @nvaccess/userDocs @nvaccess/developers
1+
# This is a comment.
2+
# Each line is a file pattern followed by one or more owners.
3+
4+
# These owners will be the default owners for everything in
5+
# the repo. Unless a later match takes precedence,
6+
# @global-owner1 and @global-owner2 will be requested for
7+
# review when someone opens a pull request.
8+
# * @global-owner1 @global-owner2
9+
10+
# Order is important; the last matching pattern takes the most
11+
# precedence. When someone opens a pull request that only
12+
# modifies JS files, only @js-owner and not the global
13+
# owner(s) will be requested for a review.
14+
# *.js @js-owner
15+
16+
# You can also use email addresses if you prefer. They'll be
17+
# used to look up users just like we do for commit author
18+
# emails.
19+
# *.go docs@example.com
20+
21+
# In this example, @doctocat owns any files in the build/logs
22+
# directory at the root of the repository and any of its
23+
# subdirectories.
24+
# /build/logs/ @doctocat
25+
26+
# The `docs/*` pattern will match files like
27+
# `docs/getting-started.md` but not further nested files like
28+
# `docs/build-app/troubleshooting.md`.
29+
# docs/* docs@example.com
30+
31+
# In this example, @octocat owns any file in an apps directory
32+
# anywhere in your repository.
33+
# apps/ @octocat
34+
35+
# In this example, @doctocat owns any file in the `/docs`
36+
# directory in the root of your repository and any of its
37+
# subdirectories.
38+
# /docs/ @doctocat
39+
40+
# Start of NVDA config
41+
42+
# By default auto request review from NV Access developer team.
43+
* @nvaccess/developers
44+
45+
# For changes to the userGuide auto request review from userDocs team
46+
/user_docs/en/userGuide.md @nvaccess/userDocs
47+
/projectDocs/dev/userGuideStandards.md @nvaccess/userDocs
48+
49+
# For various project documentation, require appropriate teams
50+
/projectDocs/community/ @nvaccess/userDocs
51+
/projectDocs/testing/ @nvaccess/userDocs @nvaccess/developers
52+
/projectDocs/issues/ @nvaccess/userDocs @nvaccess/developers
53+
/readme.md @nvaccess/userDocs @nvaccess/developers
54+
security.md @nvaccess/userDocs @nvaccess/developers
55+
CODE_OF_CONDUCT.md @nvaccess/userDocs @nvaccess/developers
56+
.github/CONTRIBUTING.md @nvaccess/userDocs @nvaccess/developers

‎.github/CONTRIBUTING.md‎

Lines changed: 16 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,16 +1,16 @@
1-
# Contributing to NVDA
2-
3-
Please note: the NVDA project has a [Citizen and Contributor Code of Conduct](../CODE_OF_CONDUCT.md).
4-
NV Access expects that all contributors and other community members will read and abide by the rules set out in this document while participating or contributing to this project.
5-
6-
The NVDA project is guided by a [product vision statement and set of principles](../projectDocs/product_vision.md).
7-
The vision and principles should be always considered when planning features and prioritizing work.
8-
9-
There are several ways in which you can contribute to the NVDA project:
10-
- [Reporting issues](../projectDocs/issues/readme.md)
11-
- [Issue triage and investigation](../projectDocs/issues/triage.md)
12-
- [Testing](../projectDocs/testing/contributing.md)
13-
- [Translating NVDA](../projectDocs/translating/readme.md)
14-
- [Code or documentation contributions](../projectDocs/dev/contributing.md)
15-
- [Setting up a development environment](../projectDocs/dev/contributing.md#overview-of-contribution-process)
16-
- [Creating add-ons](../projectDocs/dev/addons.md)
1+
# Contributing to NVDA
2+
3+
Please note: the NVDA project has a [Citizen and Contributor Code of Conduct](../CODE_OF_CONDUCT.md).
4+
NV Access expects that all contributors and other community members will read and abide by the rules set out in this document while participating or contributing to this project.
5+
6+
The NVDA project is guided by a [product vision statement and set of principles](../projectDocs/product_vision.md).
7+
The vision and principles should be always considered when planning features and prioritizing work.
8+
9+
There are several ways in which you can contribute to the NVDA project:
10+
- [Reporting issues](../projectDocs/issues/readme.md)
11+
- [Issue triage and investigation](../projectDocs/issues/triage.md)
12+
- [Testing](../projectDocs/testing/contributing.md)
13+
- [Translating NVDA](../projectDocs/translating/readme.md)
14+
- [Code or documentation contributions](../projectDocs/dev/contributing.md)
15+
- [Setting up a development environment](../projectDocs/dev/contributing.md#overview-of-contribution-process)
16+
- [Creating add-ons](../projectDocs/dev/addons.md)

‎.github/ISSUE_TEMPLATE/config.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
blank_issues_enabled: false
1+
blank_issues_enabled: false

‎.github/PULL_REQUEST_TEMPLATE/revert.md‎

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,20 @@
1-
---
2-
name: Revert PR
3-
about: Revert an existing pull request
4-
5-
---
6-
7-
### Reverts PR
8-
Reverts #issueNumber
9-
10-
### Issues fixed
11-
<!-- Issues that will be closed by reverting, i.e. the issues introduced via the PR getting reverted -->
12-
Fixes #issueNumber
13-
14-
### Issues reopened
15-
<!-- Issues that will be re-opened by reverting, i.e. the issues that were fixed via the PR getting reverted -->
16-
Reopens #issueNumber
17-
18-
### Reason for revert
19-
20-
### Can this PR be reimplemented? If so, what is required for the next attempt
1+
---
2+
name: Revert PR
3+
about: Revert an existing pull request
4+
5+
---
6+
7+
### Reverts PR
8+
Reverts #issueNumber
9+
10+
### Issues fixed
11+
<!-- Issues that will be closed by reverting, i.e. the issues introduced via the PR getting reverted -->
12+
Fixes #issueNumber
13+
14+
### Issues reopened
15+
<!-- Issues that will be re-opened by reverting, i.e. the issues that were fixed via the PR getting reverted -->
16+
Reopens #issueNumber
17+
18+
### Reason for revert
19+
20+
### Can this PR be reimplemented? If so, what is required for the next attempt

0 commit comments

Comments
 (0)