-
Notifications
You must be signed in to change notification settings - Fork 1
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 #1 from Sage-Bionetworks/bgrande/synapsefs-only
Duplicate `py-dcqc` repository and delete all files unrelated to SynapseFS
- Loading branch information
Showing
56 changed files
with
216 additions
and
2,549 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
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,3 +1,3 @@ | ||
[settings] | ||
profile = black | ||
known_first_party = dcqc | ||
known_first_party = synapsefs |
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,6 +1,6 @@ | ||
# Contributing | ||
|
||
Welcome to `dcqc` contributor's guide. | ||
Welcome to `fs-synapse` contributor's guide. | ||
|
||
This document focuses on getting any potential contributor familiarized with | ||
the development processes, but [other kinds of contributions] are also appreciated. | ||
|
@@ -16,7 +16,7 @@ behavior guidelines. | |
|
||
## Issue Reports | ||
|
||
If you experience bugs or general issues with `dcqc`, please have a look | ||
If you experience bugs or general issues with `fs-synapse`, please have a look | ||
on the [issue tracker]. | ||
If you don't see anything useful there, please feel free to fire an issue report. | ||
|
||
|
@@ -34,17 +34,17 @@ you help us to identify the root cause of the issue. | |
|
||
## Documentation Improvements | ||
|
||
You can help improve `dcqc` docs by making them more readable and coherent, or | ||
You can help improve `fs-synapse` docs by making them more readable and coherent, or | ||
by adding missing information and correcting mistakes. | ||
|
||
`dcqc` documentation uses [Sphinx] as its main documentation compiler. | ||
`fs-synapse` documentation uses [Sphinx] as its main documentation compiler. | ||
This means that the docs are kept in the same repository as the project code, and | ||
that any documentation update is done in the same way was a code contribution. | ||
The documentation is written using [CommonMark] with [MyST] extensions. | ||
|
||
:::{tip} | ||
Please notice that the [GitHub web interface] provides a quick way of | ||
propose changes in `dcqc`'s files. While this mechanism can | ||
propose changes in `fs-synapse`'s files. While this mechanism can | ||
be tricky for normal code contributions, it works perfectly fine for | ||
contributing to the docs, and can be quite handy. | ||
|
||
|
@@ -97,8 +97,8 @@ This often provides additional considerations and avoids unnecessary work. | |
3. Clone this copy to your local disk: | ||
|
||
```console | ||
git clone [email protected]:Sage-Bionetworks-Workflows/py-dcqc.git | ||
cd dcqc | ||
git clone [email protected]:Sage-Bionetworks/fs-synapse.git | ||
cd fs-synapse | ||
``` | ||
|
||
4. You should run: | ||
|
@@ -116,7 +116,7 @@ This often provides additional considerations and avoids unnecessary work. | |
pipenv run pre-commit install | ||
``` | ||
|
||
`dcqc` comes with a lot of hooks configured to automatically help the | ||
`fs-synapse` comes with a lot of hooks configured to automatically help the | ||
developer to check the code being written. | ||
|
||
### Implement your changes | ||
|
@@ -245,7 +245,7 @@ package: | |
|
||
If you are part of the group of maintainers and have correct user permissions | ||
on [PyPI], the following steps can be used to release a new version for | ||
`dcqc`: | ||
`fs-synapse`: | ||
|
||
1. Make sure all unit tests are successful. | ||
2. Tag the current commit on the main branch with a release tag, e.g., `v1.2.3`. | ||
|
@@ -291,5 +291,5 @@ on [PyPI], the following steps can be used to release a new version for | |
[tox]: https://tox.readthedocs.io/en/stable/ | ||
[virtual environment]: https://realpython.com/python-virtual-environments-a-primer/ | ||
[virtualenv]: https://virtualenv.pypa.io/en/stable/ | ||
[repository]: https://github.com/sage-bionetworks-workflows/py-dcqc | ||
[issue tracker]: https://github.com/sage-bionetworks-workflows/py-dcqc/issues | ||
[repository]: https://github.com/sage-bionetworks-workflows/py-fs-synapse | ||
[issue tracker]: https://github.com/sage-bionetworks-workflows/py-fs-synapse/issues |
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.