-
Notifications
You must be signed in to change notification settings - Fork 224
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'master' into check-links
- Loading branch information
Showing
163 changed files
with
5,150 additions
and
2,935 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,9 @@ | ||
--- | ||
name: Bug report | ||
about: Report a problem/bug to help us improve | ||
title: '' | ||
labels: bug | ||
assignees: '' | ||
|
||
--- | ||
|
||
|
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,5 @@ | ||
blank_issues_enabled: true | ||
contact_links: | ||
- name: GMT Community Forum | ||
url: https://forum.generic-mapping-tools.org/c/questions/pygmt-q-a | ||
about: Please ask questions here or find answers to common problems. |
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
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
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,42 @@ | ||
name: Style Checks | ||
|
||
on: | ||
push: | ||
branches: [ master ] | ||
pull_request: | ||
# Schedule daily tests | ||
schedule: | ||
- cron: '0 0 * * *' | ||
|
||
jobs: | ||
style_check: | ||
name: Style Checks | ||
runs-on: ubuntu-latest | ||
|
||
steps: | ||
# Checkout current git repository | ||
- name: Checkout | ||
uses: actions/checkout@v2.3.4 | ||
|
||
# Setup Miniconda | ||
- name: Set up Python | ||
uses: actions/setup-python@v2 | ||
with: | ||
python-version: 3.9 | ||
|
||
- name: Install packages | ||
run: | | ||
pip install black blackdoc docformatter flake8 pylint isort | ||
sudo apt-get install dos2unix | ||
- name: Formatting check (black, blackdoc, docformatter, flake8 and isort) | ||
run: make check | ||
|
||
- name: Linting (pylint) | ||
run: make lint | ||
|
||
- name: Ensure files use UNIX line breaks and have 644 permission | ||
run: | | ||
find . -type f -not -path '*/\.git/*' -exec grep -Iq . {} \; -exec dos2unix --quiet {} \; | ||
find . -type f -not -path '*/\.git/*' -exec grep -Iq . {} \; -exec chmod 644 {} \; | ||
if [[ $(git ls-files -m) ]]; then git --no-pager diff HEAD; exit 1; fi |
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,75 @@ | ||
# Authorship guidelines for academic papers and software archives | ||
|
||
First of all, we are deeply thankful to everyone who has helped make PyGMT | ||
what it is today. Our goal for this document is to establish guidelines | ||
for giving credit to contributors for their work. | ||
To do so, we will attempt to define: | ||
|
||
- Fair and diverse ways of providing recognition for contributors' efforts. | ||
- Define _contributions_ in a broad way: writing code and/or documentation, | ||
providing ideas, fostering the community, etc. | ||
|
||
The following are the ways in which individuals who have contributed will be | ||
recognized. | ||
|
||
> **Note**: These policies are not set in stone and may be changed to | ||
> accommodate the growth of the project or the preferences of the community. | ||
## The `AUTHORS.md` file | ||
|
||
Anyone who has contributed a pull request to the project is welcome to add | ||
themselves to the `AUTHORS.md` file. This file lives in the repository and is | ||
packaged with distributions. This is an optional process. | ||
|
||
## Changelog for each release | ||
|
||
Every time we make a release, everyone who has made a commit to the repository | ||
since the previous release will be mentioned in the changelog entry. If their | ||
full name is available on GitHub, we will use it. Otherwise, we will use the | ||
GitHub handle. This is a way of saying "Thank you". | ||
|
||
## Authorship on Zenodo archives of releases | ||
|
||
Anyone who has contributed to the repository (i.e., appears on `git log`) will | ||
be invited to be an author on the Zenodo archive of new releases. | ||
|
||
To be included as an author, you *must* add the following to the `AUTHORS.md` | ||
file of the repository: | ||
|
||
1. Full name | ||
2. Affiliation (if omitted, we will use "Unaffiliated") | ||
3. ORCID (optional) | ||
|
||
The order of authors will be defined by the number of commits to the repository | ||
(`git shortlog -sne`). The order can also be changed on a case-by-case basis. | ||
|
||
If you have contributed and do not wish to be included in Zenodo archives, | ||
there are a few options: | ||
|
||
1. Don't add yourself to `AUTHORS.md` | ||
2. Remove yourself from `AUTHORS.md` | ||
3. Indicate next to your name on `AUTHORS.md` that you do not wish to be | ||
included with something like `(not included in Zenodo)`. | ||
|
||
## Scientific publications (papers) | ||
|
||
We aim to write academic papers for most of our software packages. Ideally, we | ||
will publish updated papers for major changes or significant new components of the | ||
package. | ||
|
||
To be included as an author on the paper, you *must* satisfy the following | ||
criteria: | ||
|
||
1. Have made multiple and regular contributions to the repository, or the GMT repository, in numerous facets, such as wrapping functions, testing, and/or writing documentation. | ||
2. Have made non-coding contributions, including project administration and decision making. | ||
3. Have participated in the writing and reviewing of the paper. | ||
2. Add your full name, affiliation, and (optionally) ORCID to the paper. These | ||
can be submitted on pull requests to the corresponding paper repository. | ||
3. Write and/or read and review the manuscript in a timely manner and provide | ||
comments on the paper (even if it's just an "OK", but preferably more). | ||
|
||
The order of authors will be defined by the number of commits made since the | ||
previous major release that has an associated paper (`git shortlog | ||
vX.0.0...HEAD -sne`). The order of any author who hasn't made any commits will | ||
be decided by all authors. The order can also be changed on a case-by-case | ||
basis. |
Oops, something went wrong.