libk  Update of "merge"


Artifact ID: 402fcc60b23421e921b74fb47cb503a7816291437efe5de3bafd37304917733b
Page Name:merge
Date: 2020-05-20 21:52:55
Original User: lexi
Parent: d0eeac47c0f72cfa14cb13c143c9629ee29ff8335299254f602c2277708e3650 (diff)
Next 500a9c4b1c361127a25005f853bae8652f8bf31936144b41ba0b431cbcf535b7

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 first to make sure you can agree to the terms under which your contribution will be incorporated in the project.


export your branch with the fossil bundle command. for instance:

fossil bundle export --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 please do not use any other filehosting service.


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 a link to the bundle and the email address associated with your public key in your ticket.

if this is the first merge request you have made, you may be contacted via email to verify that the public key and merge request are yours. if any of these details are missing or your bundle fails signature verification, your ticket will be summarily rejected.

if you have any questions, please contact project personnel.