|
|
|
|
161
|
|
161
|
|
162
|
1. Before you start, **contact maintainer** and inform them that you
|
162
|
1. Before you start, **contact maintainer** and inform them that you
|
163
|
are planning to write a test. You can do this by filing an issue
|
163
|
are planning to write a test. You can do this by filing an issue
|
164
|
- in Github repo or by contacting the maintainer directly.
|
|
|
|
|
164
|
+ in pagure.io repo or by contacting the maintainer directly.
|
165
|
|
165
|
|
166
|
2. Read [Shellfu coding style][sfcs]; tests need to follow this.
|
166
|
2. Read [Shellfu coding style][sfcs]; tests need to follow this.
|
167
|
|
167
|
|
|
|
|
|
170
|
written down. A more consistent documentation is expected to arrive
|
170
|
written down. A more consistent documentation is expected to arrive
|
171
|
before `v0.1.0`.
|
171
|
before `v0.1.0`.
|
172
|
|
172
|
|
173
|
- [sfcs]: https://github.com/AloisMahdal/shellfu/blob/last/notes/style.md
|
|
|
|
|
173
|
+ [sfcs]: https://pagure.io/shellfu/src/last/notes/style.md
|