xiaoxiang781216 edited a comment on issue #527: STM32H753II URL: https://github.com/apache/incubator-nuttx/pull/527#issuecomment-597233802 > @xiaoxiang781216 > > > The better approach is append your style patch to this PR and trigger the precheck again: > > https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/committing-changes-to-a-pull-request-branch-created-from-a-fork > > Yes. That it the right approach, and I will do it that way when I have time. > > Did you add it to the work flow document? The workflow document contain many options now, and it's hard for newbie to follow up. I would prefer that the main body of workflow document just describe the best practice the most contributor use daliy, for example: 1.One method to get source code 2.One method to send PR 3.One method to rework the PR after review The reader just need follow the sequence step by step, no any if/else at all. And then the document could list other alternatives or advance usage like this in the note section. Also it's better to list the contributor workflow first, then additional committer workflow, last the advance tips.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
