forked from CleverRaven/Cataclysm-DDA
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #35 from CleverRaven/master
catchup branch
- Loading branch information
Showing
1,158 changed files
with
345,965 additions
and
276,258 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,43 @@ | ||
# options affecting formatting | ||
format: | ||
# how wide to allow formatted cmake files | ||
line_width: 100 | ||
# how many spaces to tab for indent | ||
tab_size: 4 | ||
# if true, separate flow control names from their parentheses | ||
separate_ctrl_name_with_space: true # currently ignored by cmake-lint | ||
# if true, separate function names from parentheses with a | ||
separate_fn_name_with_space: false # currently ignored by cmake-lint | ||
# if a statement is wrapped to more than one line, than dangle | ||
# the closing parenthesis on its own line. | ||
dangle_parens: false # currently ignored by cmake-lint | ||
# Format command names consistently as 'lower' or 'upper' case | ||
# 'canonical': like in official documentation | ||
command_case: 'canonical' # currently ignored by cmake-lint | ||
# Format keywords consistently as 'lower' or 'upper' case | ||
keyword_case: 'upper' # currently ignored by cmake-lint | ||
# options affecting comment reflow and formatting | ||
markup: | ||
# enable comment markup parsing and reflow | ||
enable_markup: false | ||
# options affecting linter | ||
lint: | ||
# list of lint codes to disable | ||
# C0113: Missing COMMENT in statement which allows it | ||
disabled_codes: ['C0113'] | ||
# regular expression pattern describing valid function names | ||
function_pattern: '[a-z_]+' | ||
# regular expression pattern describing valid names for private variables | ||
# WEIRD: strangely named "directory variable name" in lint output | ||
private_var_pattern: '_[0-9A-Z_]+' | ||
# regular expression pattern describing valid names for public variables (strangely named "directories"?) | ||
# WEIRD: strangely named "directory variable name" in lint output | ||
public_var_pattern: '[0-9A-Z]+' | ||
# regular expression pattern describing valid macro names | ||
macro_pattern: '[a-z_]+' | ||
# regular expression pattern describing valid names for function/macro | ||
# arguments and loop variables | ||
argument_var_pattern: '[A-Z][A-Z0-9_]+' | ||
# require no more than this many newlines between statements | ||
max_statement_spacing: 2 | ||
|
Validating CODEOWNERS rules …
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,54 +1,33 @@ | ||
<!-- HOW TO USE: Under each "#### Heading" below, enter information relevant to your pull request. | ||
Leave the headings unless they don't apply to your PR, and remove the comment blocks (surrounded with <!–– and ––>) when you are done. | ||
NOTE: Please grant permission for repository maintainers to edit your PR. It is EXTREMELY common for PRs to be held up due to trivial changes being requested and the author being unavailable to make them. | ||
--> | ||
NOTE: Please grant permission for repository maintainers to edit your PR. It is EXTREMELY common for PRs to be held up due to trivial changes being requested and the author being unavailable to make them. --> | ||
|
||
#### Summary | ||
|
||
<!-- This section should consist of exactly one line, formatted like this: | ||
SUMMARY: [Category] "[Briefly describe the change in these quotation marks]" | ||
Do not enter the square brackets []. Category must be one of these: | ||
- Features | ||
- Content | ||
- Interface | ||
- Mods | ||
- Balance | ||
- Bugfixes | ||
- Performance | ||
- Infrastructure | ||
- Build | ||
- I18N | ||
Category "Brief description" | ||
<!-- This section should consist of exactly one line, edit the one above. | ||
Category must be one of these: Features, Content, Interface, Mods, Balance, Bugfixes, Performance, Infrastructure, Build, I18N. Or replace the whole line with just the word None for no changelog entry. | ||
For more on the meaning of each category, see: | ||
https://github.com/CleverRaven/Cataclysm-DDA/blob/master/doc/CHANGELOG_GUIDELINES.md | ||
If approved and merged, your summary will be added to the project changelog: | ||
https://github.com/CleverRaven/Cataclysm-DDA/blob/master/data/changelog.txt | ||
--> | ||
https://github.com/CleverRaven/Cataclysm-DDA/blob/master/data/changelog.txt --> | ||
|
||
#### Purpose of change | ||
|
||
<!-- With a few sentences, describe your reasons for making this change. If it relates to an existing issue, you can link it with a # followed by the Github issue number, like #1234. If your pull request *fully* resolves an issue, include the word "Fix" or "Fixes" before the issue number, like: Fixes #1234. | ||
If there is no related issue, explain here what issue, feature, or other concern you are addressing. If this is a bugfix, include steps to reproduce the original bug, so your fix can be verified. | ||
--> | ||
<!-- With a few sentences, describe your reasons for making this change. If it relates to an existing issue, you can link it with a # followed by the GitHub issue number, like #1234. If your pull request *fully* resolves an issue, include the word "Fix" or "Fixes" before the issue number, like: Fixes #1234. | ||
If there is no related issue, explain here what issue, feature, or other concern you are addressing. If this is a bugfix, include steps to reproduce the original bug, so your fix can be verified. --> | ||
|
||
#### Describe the solution | ||
|
||
<!-- How does the feature work, or how does this fix a bug? The easier you make your solution to understand, the faster it can get merged. --> | ||
<!-- How does the feature work, or how does this fix a bug? The easier you make your solution to understand, the faster it can get merged. --> | ||
|
||
#### Describe alternatives you've considered | ||
|
||
<!-- Explain any alternative solutions, different approaches, or possibilities you've considered using to solve the same problem. --> | ||
|
||
#### Testing | ||
|
||
<!-- Describe what steps you took to test that this PR resolved the bug or added the feature, and what tests you performed to make sure it didn't cause any regressions. Also include testing suggestions for reviewers and maintainers. --> | ||
<!-- Describe what steps you took to test that this PR resolved the bug or added the feature, and what tests you performed to make sure it didn't cause any regressions. Also include testing suggestions for reviewers and maintainers. --> | ||
|
||
#### Additional context | ||
|
||
<!-- Add any other context (such as mock-ups, proof of concepts or screenshots) about the feature or bugfix here. --> | ||
<!-- Add any other context (such as mock-ups, proof of concepts or screenshots) about the feature or bugfix here. --> |
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
name: cmake-format linting | ||
|
||
on: | ||
push: | ||
branches: | ||
- master | ||
paths: | ||
- '**/CMakeLists.txt' | ||
- '**.cmake' | ||
- '**.cmake.in' | ||
pull_request: | ||
branches: | ||
- master | ||
paths: | ||
- '**/CMakeLists.txt' | ||
- '**.cmake' | ||
- '**.cmake.in' | ||
|
||
jobs: | ||
check: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- name: checkout repository | ||
uses: actions/checkout@v1 | ||
with: | ||
fetch-depth: 1 | ||
- name: install cmakelang | ||
run: python3 -m pip install -U cmakelang | ||
- name: run cmake-lint | ||
run: python3 -m cmakelang.lint CMakeLists.txt src/CMakeLists.txt data/CMakeLists.txt lang/CMakeLists.txt src/chkjson/CMakeLists.txt tools/format/CMakeLists.txt tools/clang-tidy-plugin/CMakeLists.txt cmake_uninstall.cmake.in -c .cmake-format.yml | ||
|
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
on: | ||
push: | ||
branches: | ||
- master | ||
paths: | ||
- 'doc/JSON_INFO.md' | ||
name: TOC Generator | ||
jobs: | ||
generateTOC: | ||
if: github.repository == 'CleverRaven/Cataclysm-DDA' | ||
name: Update the table of contents | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v2 | ||
- run: npx doctoc doc/JSON_INFO.md --github | ||
- name: Create Pull Request | ||
uses: peter-evans/create-pull-request@v3 | ||
with: | ||
commit-message: Update the table of contents | ||
branch: update-toc | ||
title: Update the table of contents in doc/JSON_INFO.md | ||
body: | | ||
```sh | ||
npx doctoc doc/JSON_INFO.md --github | ||
``` |
This file contains 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
This file contains 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
Oops, something went wrong.