View Single Post
Old 05-22-2025, 04:10 AM   #16
BeckyEbook
Guru
BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.BeckyEbook ought to be getting tired of karma fortunes by now.
 
BeckyEbook's Avatar
 
Posts: 846
Karma: 3341026
Join Date: Jan 2017
Location: Poland
Device: Various
It's not bad.
You have prepared the correct Pull Request in your fork based on the branch named "pj7-patch-1".
In this case, you need to act "bolder" and include the Pull Request in the master documentation branch based on your branch.
This is done here:
https://github.com/Sigil-Ebook/sigil...de:pj7-patch-1

Note that the left is the main "master" branch of the documentation, and the right is your "pj7-patch-1" branch with changes. The direction of the arrow is important: it must lead from your branch to the main "master" branch.

Nobody starts out as an expert.

Last edited by BeckyEbook; 05-22-2025 at 04:58 AM.
BeckyEbook is offline   Reply With Quote