Amar Takhar commented on a discussion: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/965#note_140731 You were made aware we talked about it during a meeting more than once. In fact the last time we talked about it was last month and I explicitly said that I wanted to wait until. 8.1 so I could finish the tool then out of nowhere this mad dash to make it happen for 7.1 started. I'm far more confused as to why this has happened. Nothing in the CI uses hardcoded files this happened last year when you yourself explicitly refused the ability to push to CI configs. I offered an out-of-band solution which was accepted this makes this change even more baffling. `rtems-ci-stage` if you download this tool and run it will download the config files though it's currently broken due to the AI bot blocker I'm working on a solution for that: ``` /data/tools/rtems-ci-stage -a VERSION: 1.0.0 codespell : config/codespell/codespellrc --> .codespellrc codespell : config/codespell/dictionary.txt --> .gitlab/dictionary.txt codespell : config/codespell/ignore_words.txt --> .gitlab/ignore_words.txt clang-format : config/clang/clang-format --> .clang-format yapf : config/yapf/style.yapf --> .style.yapf mdformat : config/mdformat/mdformat.toml --> .mdformat.toml yamlfmt : config/yamlfmt/yamlfmt.yml --> .yamlfmt.yml ``` You will need to run this tool regardless if you want to run any local tools including `clang-format` as it's the only way to get the parent `.clang-format` file. There's no sense in having files littered everywhere I can tell you that CI won't use them and neither with `rtems-format` as I want everything to use the same method for configuring the tools. This isn't the first time I brought up this tool or it's usage. -- View it on GitLab: https://gitlab.rtems.org/rtems/rtos/rtems/-/merge_requests/965#note_140731 You're receiving this email because of your account on gitlab.rtems.org.
_______________________________________________ bugs mailing list [email protected] http://lists.rtems.org/mailman/listinfo/bugs
