On Sun, Jun 20, 2021 at 1:13 AM Ida Delphine <idad...@gmail.com> wrote:
> Hello everyone, > I updated the hooks script. About the modes, we have the default, "strict" > and "nonstrict" (couldn't think of better names). With the default mode, it > prints a warning specifying the number of style issues if any and aborts > the commit. With the strict mode, it goes into more detail showing both the > formatted and unformatted patch, the number of style issues, and aborts the > commit. In the non-strict mode, it simply displays the warning with the > style issues and the commit happens. > > The default mode basically happens when you run > >> git commit -m "Commit message" >> > The best method I could find to pass arguments to a script was via > environment variables. So the nonstrict mode applies when you run > >> STYLEMODE=nonstrict git commit -m "Commit message" >> > The strict mode applies when you run > >> STYLEMODE=strict git commit -m "Commit message" >> > > What are the possible options to pass arguments? (Maybe, a blog post :)) Reading from a git-config file would be better than environment variables. It might be better to share screenshots by a link (e.g., a blog post :)) to avoid hitting the mailing list attachment limits. Gedare >
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
