You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am hopelessly lost in trying to propose improvements and corrections to the manual.
As per instructions I have created a fork of this repository and made changes there. But when I try to make a pull request it just says This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository. and I have no idea what to do, not can I find any instructions within the manual itself.
Part of the problem is that I have never used GitHub for anything other than personal use - not collaborating with anyone else so I probably don't understand how to make pull requests (or even what they really are).
I appreciate GitHub is a very powerful tool for projects with multiple contributors - but I really dont have the time or the inclination to learn how to use it. I've tried but the learning curve seems incredibly steep and off putting.
However I do find the Joomla dev manual a potentially very useful resource but it is full of errors, typos and incomplete or completely missing bits which sometimes I could easily correct.
Is there not someone to whom I could simply email some proposed changes and they could press whatever obscure combination of buttons is needed to make the magic happen and get corrections published. It is very frustrating to see a work with easily fixable mistakes but not have any simple way of correcting them.
Just a suggestion.
For now I will continue to annotate my fork of the manual as I see fit and just have to live with the fact that I can't contribute back to the community. Is this sensible (I don't think so). Could the process not be made simpler (it probably does seem simple to those of you who use it regularly, but to an outsider it is very obscure)
Thanks for listening.
The text was updated successfully, but these errors were encountered:
There are tools available which can help you, @robbiejackson started with one and now is the main contributor so.
I forgot which he used but found https://holocron.so/ which you might code try.
Hi Roger,
I'd like to try and help here. I've gone through the same pain as you're going through!
Is there some way to contact you directly? If you're on the Joomla Mattermost chat for example https://joomlacommunity.cloud.mattermost.com/
Regards
Robbie
I am hopelessly lost in trying to propose improvements and corrections to the manual.
As per instructions I have created a fork of this repository and made changes there. But when I try to make a pull request it just says
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
and I have no idea what to do, not can I find any instructions within the manual itself.Part of the problem is that I have never used GitHub for anything other than personal use - not collaborating with anyone else so I probably don't understand how to make pull requests (or even what they really are).
I appreciate GitHub is a very powerful tool for projects with multiple contributors - but I really dont have the time or the inclination to learn how to use it. I've tried but the learning curve seems incredibly steep and off putting.
However I do find the Joomla dev manual a potentially very useful resource but it is full of errors, typos and incomplete or completely missing bits which sometimes I could easily correct.
Is there not someone to whom I could simply email some proposed changes and they could press whatever obscure combination of buttons is needed to make the magic happen and get corrections published. It is very frustrating to see a work with easily fixable mistakes but not have any simple way of correcting them.
Just a suggestion.
For now I will continue to annotate my fork of the manual as I see fit and just have to live with the fact that I can't contribute back to the community. Is this sensible (I don't think so). Could the process not be made simpler (it probably does seem simple to those of you who use it regularly, but to an outsider it is very obscure)
Thanks for listening.
The text was updated successfully, but these errors were encountered: