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
{{ message }}
This repository was archived by the owner on Jan 5, 2024. It is now read-only.
Contributions to this repository are welcome. To make a contribution we ask that you follow a few guidelines.
4
+
5
+
## Issues and features
6
+
7
+
Before filing a bug report or making a feature request, please check the issues to make sure yours isn't a duplicate.
8
+
9
+
## Pull requests
10
+
11
+
Feel free to submit pull requests to the `develop` branch with small fixes or improvements. Before implementing new features or contributing broadly-scoped changes we ask that you first open an issue or discussion.
12
+
13
+
Before submitting a PR, please test your changes in your own fork. Please do *not* open a pull request immediately and add to it frequently during development — this will saturate the `modflowpy` organization's CI.
14
+
15
+
If `develop` changes while your work is still in progress, please rebase and fix any conflicts, then force push your branch to update the pull request.
16
+
17
+
## Commit messages
18
+
19
+
To keep the repository's commit history consistent, commit messages must conform to the following formatting conventions.
20
+
21
+
Each commit message consists of a **header**, a **body** and a **footer**. The header includes a **type**, a **scope** and a **subject**:
22
+
23
+
```
24
+
<type>(<scope>): <subject>
25
+
<BLANK LINE>
26
+
<body>
27
+
<BLANK LINE>
28
+
<footer>
29
+
```
30
+
31
+
The **header** is mandatory and its **scope** is optional. The message **body** and **footer** are also optional.
32
+
33
+
Please keep lines under 100 characters.
34
+
35
+
### Type
36
+
37
+
Must be one of the following:
38
+
39
+
***ci**: Changes to our CI configuration files and scripts (example scopes: Travis)
40
+
***docs**: Documentation only changes
41
+
***feat**: A new feature
42
+
***fix**: A bug fix
43
+
***perf**: A code change that improves performance
44
+
***refactor**: A code change that neither fixes a bug nor adds a feature
45
+
***style**: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
46
+
***test**: Adding missing tests or correcting existing tests
47
+
***revert**: Reverts a previous commit
48
+
49
+
### Scope
50
+
The scope should be the name of the FloPy module/class affected (as perceived by the person reading the changelog generated from commit messages.
51
+
52
+
There are currently a few exceptions to the "use module/class name" rule:
53
+
54
+
***release**: used when updating files prior to a release
55
+
***releasenotes**: used for updating the release notes
56
+
***readme**: used for updating the release notes in README.md
57
+
***changelog**: used for updating the release notes in CHANGELOG.md
58
+
* none/empty string: useful for `style`, `test` and `refactor` changes that are done across all
59
+
packages (e.g. `style: add missing semicolons`) and for docs changes that are not related to a
60
+
specific package (e.g. `docs: fix typo in tutorial`).
61
+
62
+
### Subject
63
+
64
+
The subject contains a succinct description of the change:
65
+
66
+
* use the imperative, present tense: "change" not "changed" nor "changes"
67
+
* don't capitalize the first letter
68
+
* do not include a dot (.) at the end
69
+
70
+
### Body
71
+
72
+
Just as in the **subject**, use the imperative, present tense: "change" not "changed" nor "changes".
73
+
The body should include the motivation for the change and contrast this with previous behavior.
74
+
75
+
### Footer
76
+
77
+
The footer should contain any information about **Breaking Changes** and is also the place to reference GitHub issues that this commit **Closes**.
78
+
79
+
**Breaking Changes** should start with the word `BREAKING CHANGE:` with a space or two newlines. The rest of the commit message is then used for this.
An action to install the [Intel OneAPI](https://www.intel.com/content/www/us/en/developer/tools/oneapi/fortran-compiler.html#gs.bksc2p) Fortran compiler.
7
6
@@ -31,9 +30,7 @@ To use this action, add a step like the following to your workflow:
Environment variables must be set before the compiler can be used. On Linux or MacOS runners, run `source /opt/intel/oneapi/setvars.sh`. On Windows, run `call "scripts/install/build_windows.bat"` from a step with `shell: cmd`.
38
-
39
-
**Note:** Environment variables are not preserved between steps, so the above must occur in the same step in which the `ifort` command is used.
36
+
The action will configure [environment variables](https://www.intel.com/content/www/us/en/develop/documentation/oneapi-programming-guide/top/oneapi-development-environment-setup.html) necessary to invoke `ifort` from subsequent workflow steps. Environment variables are not preserved between steps by default — here they are persisted by [appending to the `GITHUB_ENV` environment file](https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable).
0 commit comments