-
Notifications
You must be signed in to change notification settings - Fork 10
/
CONTRIBUTING
42 lines (30 loc) · 1.35 KB
/
CONTRIBUTING
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
Contributing code to this project
---------------------------------
It's helpful to track fixes or new features via wishlist bugs against the
'piuparts' package, eg with the 'reportbug' tool ('devscripts' package).
The BTS will ensure the developers' mailing list
is notified.
Patches can be submitted by mail (git format-patch, see below)
or as requests to pull from a publicly-visible git repository.
In either case, please make a topic branch based on the 'develop' branch.
You can send patches or requests to the development list,
or to the tracking bug: <bugnumber>@bugs.debian.org.
One possible workflow:
git clone https://salsa.debian.org/debian/piuparts.git
git checkout origin/develop -b <topicname>
<edits>
git commit -a
git format-patch -M origin/develop
reportbug piuparts
<describe the issue, attach the patch>
Does and don'ts
---------------
Please do *not* push to the develop or master branch directly, unless
explicitly asked for!
Please always *do* include a debian/changelog entry with your patches.
Please always *do* test your patches and state that you tested them.
Contributing bugs to other projects
-----------------------------------
Another very useful type of contributions are filing bug reports based
on piuparts runs. This is described in https://piuparts.debian.org/bug_howto.html