forked from travisb-ca/nitpick
-
Notifications
You must be signed in to change notification settings - Fork 0
/
repo.txt
75 lines (66 loc) · 1.58 KB
/
repo.txt
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
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
The design of the nitpick repository is meant to keep the amount of manual
merging to a minimum. Some merging will undoubtedly be necessary.
To effect this every file is named after the sha256 hash of the contents and
are referrenced as such. Within the top level .nitpick directory of the project
there is the following structure:
.nitpick/
/config/
/config - configuration file for the repository
/users - list of users for this repository
/a - indirect issue directory
/b
/c
...
/f
/0
/1
...
/9/a
/9/b
...
/9/9/99abc...f879/issue - Root issue description
/9/9/99abc...f879/ab897..abc - comment 1
/9/9/99abc...f879/feb87..876 - comment 2
Not all indirect issue directories will exist as they are created as needed.
The file formats follow a simple, easily hand editted format of some metadata
followed by two dashes, followed by the free form data. ie.
"""
Date: 2012-06-11 9:03PM (-800)
Title: Sample Issue
Severity: Minor
Priority: 1
Owner: [email protected]
State: Open
Component: Documentation
Seen_In_Build: 0.1.0
Fix_By: 1.0
Resolution:
Type: Feature
--
This is the description of the sample issue in nitpick.
"""
The specific metadata varies by object (o denotes the open ended data):
Issue:
- Component
- Date (YYYY-MM-DD HH:MM:SS in UTC time)
- Fix_By
- Owner
- Reported_By
- Priority
- Resolution
- Seen_In_Build
- Severity
- State
- Title
- Type
- Units_of_Work
- Percent_Complete
o Description
Comment:
- Attachment
- Attachment-filename
- Attachment-type
- Date (YYYY-MM-DD HH:MM:SS in UTC time)
- Parent
- User
o Comment