You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit updates the markdown files based on error reported
after updating mirrors-prettier pre-commit hook to run for the
"markdown" type in the subsequent commit.
Copy file name to clipboardexpand all lines: README.md
+9-11
Original file line number
Diff line number
Diff line change
@@ -35,21 +35,19 @@ This will mark the version of the template file used and the Slicer version in t
35
35
36
36
### Which version of Slicer do the generated application build against ?
37
37
38
-
Leveraging the ``jinja2-github`` plugin, the ``cookiecutter`` template generator will retrieve the latest commit associated with the Slicer repository default branch and it will set it as ``GIT_TAG`` value in the generated ``CMakeLists.txt``.
39
-
40
-
38
+
Leveraging the `jinja2-github` plugin, the `cookiecutter` template generator will retrieve the latest commit associated with the Slicer repository default branch and it will set it as `GIT_TAG` value in the generated `CMakeLists.txt`.
41
39
42
40
## License
43
41
44
42
This project template is distributed under the Apache 2.0 license. Please see
Copy file name to clipboardexpand all lines: {{cookiecutter.project_name}}/BUILD.md
+13-17
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,25 @@
1
-
Build and Package {{cookiecutter.project_name}}
2
-
==============================
1
+
# Build and Package {{cookiecutter.project_name}}
3
2
4
3
This document summarizes how to build and package {{cookiecutter.project_name}} on Windows.
5
4
6
5
{{cookiecutter.project_name}} is a custom Slicer application. Reading the [3D Slicer Developer Documentation](https://slicer.readthedocs.io/en/latest/developer_guide/index.html) may help answer additional questions.
7
6
8
7
The initial source files were created using [KitwareMedical/SlicerCustomAppTemplate](https://github.com/KitwareMedical/SlicerCustomAppTemplate).
9
8
10
-
Prerequisites
11
-
-------------
9
+
## Prerequisites
12
10
13
-
* Setting up your git account:
11
+
- Setting up your git account:
14
12
15
-
* Create a [Github](https://github.com) account.
13
+
- Create a [Github](https://github.com) account.
16
14
17
-
* Setup your SSH keys following [these](https://help.github.com/articles/generating-ssh-keys) instructions.
15
+
- Setup your SSH keys following [these](https://help.github.com/articles/generating-ssh-keys) instructions.
18
16
19
-
* Setup [your git username](https://help.github.com/articles/setting-your-username-in-git) and [your git email](https://help.github.com/articles/setting-your-email-in-git).
17
+
- Setup [your git username](https://help.github.com/articles/setting-your-username-in-git) and [your git email](https://help.github.com/articles/setting-your-email-in-git).
20
18
21
-
* If not already done, email `FirstName LastName <firstname.lastname@{{cookiecutter.github_organization}}.com>` to be granted access to
19
+
- If not already done, email `FirstName LastName <firstname.lastname@{{cookiecutter.github_organization}}.com>` to be granted access to
22
20
the [{{cookiecutter.github_organization}}/{{cookiecutter.github_project}}](https://github.com/{{cookiecutter.github_organization}}/{{cookiecutter.github_project}}) repository.
23
21
24
-
Checkout
25
-
--------
22
+
## Checkout
26
23
27
24
1. Start `Git Bash`
28
25
2. Checkout the source code into a directory `C:\W\` by typing the following commands:
Note: use short source and build directory names to avoid the [maximum path length limitation](https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#maximum-path-length-limitation).
38
35
39
-
Build
40
-
-----
36
+
## Build
37
+
41
38
Note: The build process will take approximately 3 hours.
42
39
43
40
<b>Option 1: CMake GUI and Visual Studio (Recommended)</b>
44
41
45
42
1. Start [CMake GUI](https://cmake.org/runningcmake/), select source directory `C:\W\{{cookiecutter.github_project|first}}` and set build directory to `C:\W\{{cookiecutter.github_project|first}}R`.
46
43
2. Add an entry `Qt5_DIR` pointing to `C:/Qt/${QT_VERSION}/${COMPILER}/lib/cmake/Qt5`.
47
-
2. Generate the project.
48
-
3. Open `C:\W\{{cookiecutter.github_project|first}}R\{{cookiecutter.project_name}}.sln`, select `Release` and build the project.
44
+
3. Generate the project.
45
+
4. Open `C:\W\{{cookiecutter.github_project|first}}R\{{cookiecutter.project_name}}.sln`, select `Release` and build the project.
49
46
50
47
<b>Option 2: Command Line</b>
51
48
@@ -60,8 +57,7 @@ cmake -G "Visual Studio 17 2022" -A x64 -DQt5_DIR:PATH=`C:/Qt/${QT_VERSION}/${CO
Copy file name to clipboardexpand all lines: {{cookiecutter.project_name}}/CONTRIBUTING.md
+15-17
Original file line number
Diff line number
Diff line change
@@ -1,23 +1,21 @@
1
-
Contributing to {{cookiecutter.project_name}}
2
-
===============================
1
+
# Contributing to {{cookiecutter.project_name}}
3
2
4
3
There are many ways to contribute to {{cookiecutter.project_name}}.
5
4
6
-
* Submit a feature request or bug, or add to the discussion on the [{{cookiecutter.project_name}} issue tracker][is]
7
-
* Submit a [Pull Request][pr] to improve {{cookiecutter.project_name}}.
5
+
- Submit a feature request or bug, or add to the discussion on the [{{cookiecutter.project_name}} issue tracker][is]
6
+
- Submit a [Pull Request][pr] to improve {{cookiecutter.project_name}}.
8
7
9
-
The PR Process, and Related Gotchas
10
-
-----------------------------------
8
+
## The PR Process, and Related Gotchas
11
9
12
-
####How to submit a PR ?
10
+
### How to submit a PR ?
13
11
14
12
If you are new to {{cookiecutter.project_name}} development and you don't have push access to the {{cookiecutter.project_name}}
15
13
repository, here are the steps:
16
14
17
15
1.[Fork and clone][fk] the repository.
18
-
3. Create a branch.
19
-
4.[Push][push] the branch to your GitHub fork.
20
-
5. Create a [Pull Request][pr].
16
+
2. Create a branch.
17
+
3.[Push][push] the branch to your GitHub fork.
18
+
4. Create a [Pull Request][pr].
21
19
22
20
This corresponds to the `Fork & Pull Model` described in the [GitHub documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/getting-started/about-collaborative-development-models)
23
21
guides.
@@ -37,17 +35,17 @@ comments posted by the reviewers, you may have to revisit your patches.
37
35
Getting your contributions integrated is relatively straightforward, here
38
36
is the checklist:
39
37
40
-
* All tests pass
41
-
* Consensus is reached. This usually means that at least one reviewer added a `LGTM` comment
42
-
and a reasonable amount of time passed without anyone objecting. `LGTM` is an
43
-
acronym for _Looks Good to Me_.
38
+
- All tests pass
39
+
- Consensus is reached. This usually means that at least one reviewer added a `LGTM` comment
40
+
and a reasonable amount of time passed without anyone objecting. `LGTM` is an
41
+
acronym for _Looks Good to Me_.
44
42
45
43
Next, there are two scenarios:
46
-
* You do NOT have push access: A {{cookiecutter.project_name}} core developer will integrate your PR.
47
-
* You have push access: Simply click on the "Merge pull request" button.
48
44
49
-
Then, click on the "Delete branch" button that appears afterward.
45
+
- You do NOT have push access: A {{cookiecutter.project_name}} core developer will integrate your PR.
46
+
- You have push access: Simply click on the "Merge pull request" button.
50
47
48
+
Then, click on the "Delete branch" button that appears afterward.
0 commit comments