D 2020-05-20T22:41:06.199
L merge
N text/x-markdown
P 402fcc60b23421e921b74fb47cb503a7816291437efe5de3bafd37304917733b
U lexi
W 1766
# merge requests
while libk is developed primarily by a core of trusted developers with check-in privileges, we also welcome external contributions. unfortunately, fossil does not have an integrated merge request system. until we can automate something, please follow the instructions on this page. but don't forget to check the [legalese](wiki?name=legal) first to make sure you can agree to the terms under which your contribution will be incorporated in the project.
## bundling
export your branch with the [fossil bundle](https://c.comint.su/libk/help?cmd=bundle) command. for instance:
fossil bundle export libk-better-strings.br --branch better-strings
please make sure to give your branch a meaningful name. once you have exported it, sign the bundle with signify and make it bundle available via HTTP. you may place the bundle on a server you control, or upload it to [0x0.st](https://0x0.st). please do not use any other filehosting service.
## ticketing
after you have bundled your branch, open a new ticket of type "merge-request". you may do this even without an account by logging in as "anonymous" and completing the captcha correctly. include the bundle signature, a link to the bundle, and the email address associated with your public key in your ticket. your email address will not be displayed publicly.
if this is the first merge request you have made, you will be contacted via email to retrieve your public key. if any of the listed details are missing or your bundle fails signature verification, your ticket will be summarily rejected. if you do not respond to the verification email within 24 hours, your ticket will be purged as spam.
if you have any questions, please contact [project personnel](wiki?name=roster).
Z aad211a0ee5789b8e81ab75ef41b09f1