Skip to content

Commit 9c9b3eb

Browse files
CONTRIBUTING.md: Move PR link
1 parent 1eaf184 commit 9c9b3eb

File tree

1 file changed

+15
-15
lines changed

1 file changed

+15
-15
lines changed

CONTRIBUTING.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -30,21 +30,21 @@ in Yosys can be helpful for this process.
3030
# Using pull requests
3131

3232
If you are working on something to add to Yosys, or fix something that isn't
33-
working quite right, make a PR! An open PR, even as a draft, tells everyone
34-
that you're working on it and they don't have to. It can also be a useful way
35-
to solicit feedback on in-progress changes. See below to find the best way to
36-
[ask us questions](#asking-questions).
37-
38-
In general, all changes to the code are done as a
39-
[PR](https://github.com/YosysHQ/yosys/pulls), with [Continuous Integration
40-
(CI)](https://github.com/YosysHQ/yosys/actions) tools that automatically run the
41-
full suite of tests compiling and running Yosys. Please make use of this! If
42-
you're adding a feature: add a test! Not only does it verify that your feature
43-
is working as expected, but it can also be a handy way for people to see how the
44-
feature is used. If you're fixing a bug: add a test! If you can, do this
45-
first; it's okay if the test starts off failing - you already know there is a
46-
bug. CI also helps to make sure that your changes still work under a range of
47-
compilers, settings, and targets.
33+
working quite right, make a [PR](https://github.com/YosysHQ/yosys/pulls)! An
34+
open PR, even as a draft, tells everyone that you're working on it and they
35+
don't have to. It can also be a useful way to solicit feedback on in-progress
36+
changes. See below to find the best way to [ask us
37+
questions](#asking-questions).
38+
39+
In general, all changes to the code are done as a PR, with [Continuous
40+
Integration (CI)](https://github.com/YosysHQ/yosys/actions) tools that
41+
automatically run the full suite of tests compiling and running Yosys. Please
42+
make use of this! If you're adding a feature: add a test! Not only does it
43+
verify that your feature is working as expected, but it can also be a handy way
44+
for people to see how the feature is used. If you're fixing a bug: add a test!
45+
If you can, do this first; it's okay if the test starts off failing - you
46+
already know there is a bug. CI also helps to make sure that your changes still
47+
work under a range of compilers, settings, and targets.
4848

4949

5050
### Labels

0 commit comments

Comments
 (0)