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
Copy file name to clipboardexpand all lines: .build_rtd_docs/MAINPAGE.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,6 @@
2
2
3
3
The documentation here is extracted from the source code by [doxygen](https://www.doxygen.nl/index.html).
4
4
5
-
The source code repository is hosted [on GitHub](https://github.com/MODFLOW-USGS/modflow6).
5
+
The source code repository is hosted [on GitHub](https://github.com/MODFLOW-ORG/modflow6).
6
6
7
7
This documentation is intended for MODFLOW 6 contributors and users of the MODFLOW 6 library/API. MODFLOW 6 usage documentation can be found [on ReadTheDocs](https://modflow6.readthedocs.io/en/latest/).
-[ ] Updated [develop.tex](/MODFLOW-USGS/modflow6/doc/ReleaseNotes/develop.tex) with a plain-language description of the bug fix, change, feature; required for changes that may affect users
15
-
-[ ] Updated [input and output guide](/MODFLOW-USGS/modflow6/doc/mf6io)
-[ ] Updated [develop.tex](/MODFLOW-ORG/modflow6/doc/ReleaseNotes/develop.tex) with a plain-language description of the bug fix, change, feature; required for changes that may affect users
15
+
-[ ] Updated [input and output guide](/MODFLOW-ORG/modflow6/doc/mf6io)
16
16
-[ ] Removed checklist items not relevant to this pull request
17
17
18
-
For additional information see [instructions for contributing](/MODFLOW-USGS/modflow6/.github/CONTRIBUTING.md) and [instructions for developing](/MODFLOW-USGS/modflow6/.github/DEVELOPER.md).
18
+
For additional information see [instructions for contributing](/MODFLOW-ORG/modflow6/.github/CONTRIBUTING.md) and [instructions for developing](/MODFLOW-ORG/modflow6/.github/DEVELOPER.md).
Copy file name to clipboardexpand all lines: .github/workflows/release.yml
+9-9
Original file line number
Diff line number
Diff line change
@@ -14,12 +14,12 @@ on:
14
14
required: true
15
15
type: string
16
16
compiler_toolchain:
17
-
description: 'Compiler toolchain to use. For supported options see https://github.com/MODFLOW-USGS/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
17
+
description: 'Compiler toolchain to use. For supported options see https://github.com/MODFLOW-ORG/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
18
18
required: false
19
19
type: string
20
20
default: 'intel-classic'
21
21
compiler_version:
22
-
description: 'Compiler version to use. For supported options see https://github.com/MODFLOW-USGS/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
22
+
description: 'Compiler version to use. For supported options see https://github.com/MODFLOW-ORG/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
Copy file name to clipboardexpand all lines: .github/workflows/release_dispatch.yml
+3-3
Original file line number
Diff line number
Diff line change
@@ -25,12 +25,12 @@ on:
25
25
required: true
26
26
type: string
27
27
compiler_toolchain:
28
-
description: 'Compiler toolchain to use. For supported options see https://github.com/MODFLOW-USGS/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
28
+
description: 'Compiler toolchain to use. For supported options see https://github.com/MODFLOW-ORG/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
29
29
required: false
30
30
type: string
31
31
default: 'intel-classic'
32
32
compiler_version:
33
-
description: 'Compiler version to use. For supported options see https://github.com/MODFLOW-USGS/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
33
+
description: 'Compiler version to use. For supported options see https://github.com/MODFLOW-ORG/modflow6/blob/develop/DEVELOPER.md#compiler-compatibility.'
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -45,11 +45,11 @@ We want to fix all issues as soon as possible, but we first need to reproduce an
45
45
46
46
Please provide such an example. This saves maintainers time and ultimately allows us to fix more bugs. While we understand it might be difficult to isolate the essence of a problem, bugs can only be investigated or fixed if problems are accurately identified. Issues lacking sufficient information to reproduce may be closed.
47
47
48
-
File an issue by filling out our [issue form](https://github.com/MODFLOW-USGS/modflow6/issues/new).
48
+
File an issue by filling out our [issue form](https://github.com/MODFLOW-ORG/modflow6/issues/new).
49
49
50
50
### Questions
51
51
52
-
Please do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests. Questions can be asked on the [discussions page](https://github.com/MODFLOW-USGS/modflow6/discussions) under the Q&A category or on [Stack Overflow](https://stackoverflow.com/questions/tagged/modflow6) with tag `modflow6`.
52
+
Please do not open issues for general support questions as we want to keep GitHub issues for bug reports and feature requests. Questions can be asked on the [discussions page](https://github.com/MODFLOW-ORG/modflow6/discussions) under the Q&A category or on [Stack Overflow](https://stackoverflow.com/questions/tagged/modflow6) with tag `modflow6`.
53
53
54
54
We will systematically close all issues that are requests for general support.
55
55
@@ -64,8 +64,8 @@ If you would like to implement a new feature:
64
64
65
65
To submit a pull request (PR):
66
66
67
-
1. To avoid duplicating effort, [search](https://github.com/MODFLOW-USGS/modflow6/pulls) for an open or closed PR that relates to your submission.
68
-
2. Fork the MODFLOW-USGS/modflow6 repo and make your changes in a new branch, following our style and commit message guidelines and [including appropriate test cases](./DEVELOPER.md#writing-tests).
67
+
1. To avoid duplicating effort, [search](https://github.com/MODFLOW-ORG/modflow6/pulls) for an open or closed PR that relates to your submission.
68
+
2. Fork the MODFLOW-ORG/modflow6 repo and make your changes in a new branch, following our style and commit message guidelines and [including appropriate test cases](./DEVELOPER.md#writing-tests).
69
69
3.[Check the spelling and formatting](./DEVELOPER.md#formatting) of any modified or new Fortran source files, python files definition files, markdown, and LaTeX files.
70
70
4.[Rebuild makefiles](./DEVELOPER.md#generating-makefiles) and update MSVS project files if you added, removed, or renamed any source files.
71
71
5.[Run the full test suite](./DEVELOPER.md#running-tests) and make sure all tests pass.
@@ -100,7 +100,7 @@ Adherence to commit message formatting rules results in consistent messages and
100
100
101
101
Each commit message consists of three components: **header** (required), **body** (optional) and **footer** (optional). The header has three subcomponents: **type** (required), **scope** (optional) and **subject** (required):
102
102
103
-
See [the develop branch history](https://github.com/MODFLOW-USGS/modflow6/commits/develop) to get a sense for the commit style.
103
+
See [the develop branch history](https://github.com/MODFLOW-ORG/modflow6/commits/develop) to get a sense for the commit style.
Copy file name to clipboardexpand all lines: DEVELOPER.md
+10-10
Original file line number
Diff line number
Diff line change
@@ -202,7 +202,7 @@ Visual Studio installers can be downloaded from the [official website](https://v
202
202
203
203
*Doxygen & LaTeX*
204
204
205
-
[Doxygen](https://www.doxygen.nl/index.html) is used to generate the [MODFLOW 6 source code documentation](https://modflow-usgs.github.io/modflow6/). [Graphviz](https://graphviz.org/) is used by doxygen to produce source code diagrams. [LaTeX](https://www.latex-project.org/) is used to generate the MODFLOW 6 release notes and Input/Output documents.
205
+
[Doxygen](https://www.doxygen.nl/index.html) is used to generate the [MODFLOW 6 source code documentation](https://MODFLOW-ORG.github.io/modflow6/). [Graphviz](https://graphviz.org/) is used by doxygen to produce source code diagrams. [LaTeX](https://www.latex-project.org/) is used to generate the MODFLOW 6 release notes and Input/Output documents.
206
206
207
207
These programs can be installed from various sources, including by conda, macports, or from individual sources such as https://www.tug.org/. Details about USGS LaTeX libraries can be seen in addition to linux installs in the CI workflow for the docs (`.github/workflows/ci-docs.yml`).
208
208
@@ -212,7 +212,7 @@ These programs can be installed from various sources, including by conda, macpor
212
212
Fork and clone the MODFLOW 6 repository:
213
213
214
214
1. Login to your GitHub account or create one by following the instructions given [here](https://github.com/signup/free).
215
-
2.[Fork](http://help.github.com/forking) the [main MODFLOW 6](https://github.com/MODFLOW-USGS/modflow6).
215
+
2.[Fork](http://help.github.com/forking) the [main MODFLOW 6](https://github.com/MODFLOW-ORG/modflow6).
216
216
3. Clone your fork of the MODFLOW 6 repository and create an `upstream` remote pointing back to your fork.
217
217
218
218
After forking the MODFLOW 6 repository on GitHub.
@@ -232,7 +232,7 @@ cd modflow6
232
232
3. Add the main MODFLOW 6 repository as an upstream remote to your repository.
@@ -302,7 +302,7 @@ Like MODFLOW 6, `flopy` is modular — for each MODFLOW 6 package there is g
302
302
303
303
#### `modflow-devtools`
304
304
305
-
The tests use a set of shared fixtures and utilities provided by the [`modflow-devtools`](https://github.com/MODFLOW-USGS/modflow-devtools) package.
305
+
The tests use a set of shared fixtures and utilities provided by the [`modflow-devtools`](https://github.com/MODFLOW-ORG/modflow-devtools) package.
306
306
307
307
## Building
308
308
@@ -517,11 +517,11 @@ As mentioned above, binaries live in the `bin` subdirectory of the project root.
517
517
518
518
- local development binaries in the top-level `bin`
519
519
- binaries rebuilt in development mode from the latest MODFLOW 6 release in `bin/rebuilt/`
520
-
- related programs installed from the [executables distribution](https://github.com/MODFLOW-USGS/executables/releases) in `bin/downloaded/`
520
+
- related programs installed from the [executables distribution](https://github.com/MODFLOW-ORG/executables/releases) in `bin/downloaded/`
521
521
522
522
##### Rebuilding release binaries
523
523
524
-
Tests require the latest official MODFLOW 6 release to be compiled in develop mode with the same Fortran compiler as the development version. A number of binaries distributed from the [executables repo](https://github.com/MODFLOW-USGS/executables) must also be installed. The script `autotest/get_exes.py` does both of these things. It can be run from the project root with:
524
+
Tests require the latest official MODFLOW 6 release to be compiled in develop mode with the same Fortran compiler as the development version. A number of binaries distributed from the [executables repo](https://github.com/MODFLOW-ORG/executables) must also be installed. The script `autotest/get_exes.py` does both of these things. It can be run from the project root with:
525
525
526
526
```shell
527
527
pixi run get-exes
@@ -575,9 +575,9 @@ pixi run update-fortran-definitions
575
575
576
576
Some autotests load models from external repositories:
See the [MODFLOW devtools documentation](https://modflow-devtools.readthedocs.io/en/latest/md/install.html#installing-external-model-repositories) for instructions to install external model repositories.
583
583
@@ -789,7 +789,7 @@ The framework has three hooks:
789
789
790
790
A test script conventionally contains one or more test cases, fed to the test function as `idx, name` pairs. `idx` can be used to index parameter values or expected results for a specific test case. The test case `name` is useful for model/subdirectory naming, etc.
791
791
792
-
The framework will not run an unknown program. The path to any program under test (or used for a comparison) must be registered in the `targets` dictionary. Keys are strings. See `autotest/conftest.py` for the contents of `targets`— naming follows the [executables distribution](https://github.com/MODFLOW-USGS/executables).
792
+
The framework will not run an unknown program. The path to any program under test (or used for a comparison) must be registered in the `targets` dictionary. Keys are strings. See `autotest/conftest.py` for the contents of `targets`— naming follows the [executables distribution](https://github.com/MODFLOW-ORG/executables).
0 commit comments