Update APP_URL (#364)
The project was moved into the new organization 2023-05-30, but old URLs are still working due to automatic redirects by GitHub. https://github.com/wireviz/WireViz/issues/316#issuecomment-1568748914 Co-authored-by: kvid <kvid@users.noreply.github.com>
This commit is contained in:
parent
32a62a6dd7
commit
ceaad3c39a
@ -1,6 +1,6 @@
|
|||||||
# Contribution Guidelines
|
# Contribution Guidelines
|
||||||
|
|
||||||
When contributing to this repository, please [submit a new issue](https://github.com/formatc1702/WireViz/issues) first to discuss the proposed change, before submitting a pull request.
|
When contributing to this repository, please [submit a new issue](https://github.com/wireviz/WireViz/issues) first to discuss the proposed change, before submitting a pull request.
|
||||||
|
|
||||||
## Submitting a new Issue
|
## Submitting a new Issue
|
||||||
|
|
||||||
@ -27,7 +27,7 @@ When contributing to this repository, please [submit a new issue](https://github
|
|||||||
1. Push the changes to your fork.
|
1. Push the changes to your fork.
|
||||||
1. Please format your code using [`isort`](https://pycqa.github.io/isort/) and [`black`](https://black.readthedocs.io) before submitting.
|
1. Please format your code using [`isort`](https://pycqa.github.io/isort/) and [`black`](https://black.readthedocs.io) before submitting.
|
||||||
1. Submit a new pull request, using `dev` as the base branch.
|
1. Submit a new pull request, using `dev` as the base branch.
|
||||||
- If your code changes or extends the WireViz YAML syntax, be sure to update the [syntax description document](https://github.com/formatc1702/WireViz/blob/dev/docs/syntax.md) in your PR.
|
- If your code changes or extends the WireViz YAML syntax, be sure to update the [syntax description document](https://github.com/wireviz/WireViz/blob/dev/docs/syntax.md) in your PR.
|
||||||
1. Please include in the PR description (and optionally also in the commit message body) a reference (# followed by issue number) to the issue where the suggested changes are discussed.
|
1. Please include in the PR description (and optionally also in the commit message body) a reference (# followed by issue number) to the issue where the suggested changes are discussed.
|
||||||
|
|
||||||
### Hints
|
### Hints
|
||||||
|
|||||||
@ -2,7 +2,7 @@
|
|||||||
|
|
||||||
<!--
|
<!--
|
||||||
The following text is taken from #118
|
The following text is taken from #118
|
||||||
https://github.com/formatc1702/WireViz/pull/118
|
https://github.com/wireviz/WireViz/pull/118
|
||||||
|
|
||||||
TODO: write a better explaination -->
|
TODO: write a better explaination -->
|
||||||
|
|
||||||
|
|||||||
@ -499,7 +499,7 @@ The following colors are understood:
|
|||||||
- `GD`  (gold)
|
- `GD`  (gold)
|
||||||
|
|
||||||
<!-- color list generated with a helper script: -->
|
<!-- color list generated with a helper script: -->
|
||||||
<!-- https://gist.github.com/formatc1702/3c93fb4c5e392364899283f78672b952 -->
|
<!-- https://gist.github.com/17o2/3c93fb4c5e392364899283f78672b952 -->
|
||||||
|
|
||||||
It is also possible to specify colors as hexadecimal RGB values, e.g. `#112233` or `#FFFF00:#009900`.
|
It is also possible to specify colors as hexadecimal RGB values, e.g. `#112233` or `#FFFF00:#009900`.
|
||||||
Remember quoting strings containing a `#` in the YAML file.
|
Remember quoting strings containing a `#` in the YAML file.
|
||||||
|
|||||||
@ -5,4 +5,4 @@ __version__ = "0.4-dev251"
|
|||||||
|
|
||||||
CMD_NAME = "wireviz" # Lower case command and module name
|
CMD_NAME = "wireviz" # Lower case command and module name
|
||||||
APP_NAME = "WireViz" # Application name in texts meant to be human readable
|
APP_NAME = "WireViz" # Application name in texts meant to be human readable
|
||||||
APP_URL = "https://github.com/formatc1702/WireViz"
|
APP_URL = "https://github.com/wireviz/WireViz"
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user