Question about Github bug reports

@Riley Sullivan wrote > Do I need to discuss [my long list of bugs] on the musescore.org forums first before reporting them on Github, or can I just go ahead and report them on Github right away? (And yes, I would try to make sure that they haven't been reported already.)

Yes. Generally there a few recommendations for posting MuseScore 4 bug reports on Github:

    1) compile a list of steps to replicate—ideally so the issue can be recreated from scratch.
        If that's not possible, then submit a score with steps to replicate from there.

    2) report first here on the .org forum to see if others can confirm the behavior

    3) search Github for previous reports on the topic. If found, add a link to your .org posts.

    4) If you can't find an existing report Github then open a new Github Issue report.

Regarding requests and suggestions, there is a discussion area on Github. Alternatively a Github Issue can be logged as a Request. But again, it's helpful to open a discussions here first because:

    • lot's of .org follows don't read the Github posts

    • .org discussions often refine the issue and shed more light, before posting to Github.

    • this can help keep Github from becoming cluttered with dups or bum steer posts.

scorster

Report them on github. No one guarantees that your report here will be transferred to github by someone.
But first, try to find if this has been reported before to avoid duplicates.

You wrote:
Hi. I'm new on these forums, but I've been using MuseScore since it was at version 1.3.

Welcome aboard to the best forum on the internet!

(What took you so long?)