Closed rudymatela closed 2 years ago
History was quite messy up to this point. So I squashed my changes now.
@fatho and @ReinierMaas, in this PR I try to document the behaviour of merge trains well so that:
I also slightly improved inline (Haddock) code documentation.
Please let me know your thoughts or if you have any suggestions.
... when reviewing the readme.md
I recommend looking at the "rich diff".
@ReinierMaas Thanks for the review.
I believe to have addressed your comments in 465bb923c2b5e7696e22947d4cee9cefd55ae6a7, 91d8eac9db7fc51375e1609e69745e110eaf224e and 1724c9c6d0170032028fca897b768022b5485332. Can you please take a look again?
Almost done. Two more nits
:runner: Fixed! :smile:
I will merge now so I can prepare a release and deployment for tomorrow early morning. (The two nits were fixed :grin: If you have further comments let me know and I can try to address them in further PRs.)
@OpsBotPrime merge
Pull request approved for merge by @rudymatela, rebasing now.
Rebased as e0cd286121a38e89561e0dfc732ac6de4bb73d9b, waiting for CI …
CI job :yellow_circle: started.
Closes: #169
This PR documents current behaviour with regards to merge trains:
TODO