17 enum trailer_if_exists
{
19 EXISTS_ADD_IF_DIFFERENT_NEIGHBOR
,
20 EXISTS_ADD_IF_DIFFERENT
,
25 enum trailer_if_missing
{
31 int trailer_set_where(enum trailer_where
*item
, const char *value
);
32 int trailer_set_if_exists(enum trailer_if_exists
*item
, const char *value
);
33 int trailer_set_if_missing(enum trailer_if_missing
*item
, const char *value
);
36 * A list that represents newly-added trailers, such as those provided
37 * with the --trailer command line option of git-interpret-trailers.
39 struct new_trailer_item
{
40 struct list_head list
;
44 enum trailer_where where
;
45 enum trailer_if_exists if_exists
;
46 enum trailer_if_missing if_missing
;
49 struct process_trailer_options
{
58 const struct strbuf
*separator
;
59 const struct strbuf
*key_value_separator
;
60 int (*filter
)(const struct strbuf
*, void *);
64 #define PROCESS_TRAILER_OPTIONS_INIT {0}
66 void parse_trailers_from_config(struct list_head
*config_head
);
68 void parse_trailers_from_command_line_args(struct list_head
*arg_head
,
69 struct list_head
*new_trailer_head
);
71 void process_trailers_lists(struct list_head
*head
,
72 struct list_head
*arg_head
);
75 * Given some input string "str", return a pointer to an opaque trailer_block
76 * structure. Also populate the trailer_objects list with parsed trailer
77 * objects. Internally this calls trailer_info_get() to get the opaque pointer,
78 * but does some extra work to populate the trailer_objects linked list.
80 * The opaque trailer_block pointer can be used to check the position of the
81 * trailer block as offsets relative to the beginning of "str" in
82 * trailer_block_start() and trailer_block_end().
83 * blank_line_before_trailer_block() returns 1 if there is a blank line just
84 * before the trailer block. All of these functions are useful for preserving
85 * the input before and after the trailer block, if we were to write out the
86 * original input (but with the trailer block itself modified); see
87 * builtin/interpret-trailers.c for an example.
89 * For iterating through the parsed trailer block (if you don't care about the
90 * position of the trailer block itself in the context of the larger string text
91 * from which it was parsed), please see trailer_iterator_init() which uses the
92 * trailer_block struct internally.
94 * Lastly, callers should call trailer_info_release() when they are done using
97 * NOTE: Callers should treat both trailer_block and trailer_objects as
98 * read-only items, because there is some overlap between the two (trailer_block
99 * has "char **trailers" string array, and trailer_objects will have the same
100 * data but as a linked list of trailer_item objects). This API does not perform
101 * any synchronization between the two. In the future we should be able to
102 * reduce the duplication and use just the linked list.
104 struct trailer_block
*parse_trailers(const struct process_trailer_options
*,
106 struct list_head
*trailer_objects
);
109 * Return the offset of the start of the trailer block. That is, 0 is the start
110 * of the input ("str" in parse_trailers()) and some other positive number
111 * indicates how many bytes we have to skip over before we get to the beginning
112 * of the trailer block.
114 size_t trailer_block_start(struct trailer_block
*);
117 * Return the end of the trailer block, again relative to the start of the
120 size_t trailer_block_end(struct trailer_block
*);
123 * Return 1 if the trailer block had an extra newline (blank line) just before
126 int blank_line_before_trailer_block(struct trailer_block
*);
129 * Free trailer_block struct.
131 void trailer_block_release(struct trailer_block
*);
133 void trailer_config_init(void);
134 void format_trailers(const struct process_trailer_options
*,
135 struct list_head
*trailers
,
137 void free_trailers(struct list_head
*);
140 * Convenience function to format the trailers from the commit msg "msg" into
141 * the strbuf "out". Reuses format_trailers() internally.
143 void format_trailers_from_commit(const struct process_trailer_options
*,
148 * An interface for iterating over the trailers found in a particular commit
151 * struct trailer_iterator iter;
152 * trailer_iterator_init(&iter, msg);
153 * while (trailer_iterator_advance(&iter))
154 * ... do something with iter.key and iter.val ...
155 * trailer_iterator_release(&iter);
157 struct trailer_iterator
{
159 * Raw line (e.g., "foo: bar baz") before being parsed as a trailer
160 * key/val pair as part of a trailer block (as the "key" and "val"
161 * fields below). If a line fails to parse as a trailer, then the "key"
162 * will be the entire line and "val" will be the empty string.
170 struct trailer_block
*trailer_block
;
176 * Initialize "iter" in preparation for walking over the trailers in the commit
177 * message "msg". The "msg" pointer must remain valid until the iterator is
180 * After initializing, note that key/val will not yet point to any trailer.
181 * Call advance() to parse the first one (if any).
183 void trailer_iterator_init(struct trailer_iterator
*iter
, const char *msg
);
186 * Advance to the next trailer of the iterator. Returns 0 if there is no such
187 * trailer, and 1 otherwise. The key and value of the trailer can be
188 * fetched from the iter->key and iter->value fields (which are valid
189 * only until the next advance).
191 int trailer_iterator_advance(struct trailer_iterator
*iter
);
194 * Release all resources associated with the trailer iteration.
196 void trailer_iterator_release(struct trailer_iterator
*iter
);
199 * Augment a file to add trailers to it by running git-interpret-trailers.
200 * This calls run_command() and its return value is the same (i.e. 0 for
201 * success, various non-zero for other errors). See run-command.h.
203 int amend_file_with_trailers(const char *path
, const struct strvec
*trailer_args
);
205 #endif /* TRAILER_H */