René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Option to auto-fill the filename as the scope when commiting single file using the CLI","articleBody":"### Description\r\n\r\nI like using the `scope` descriptor to see which files a commit is altering\r\n\r\nIf I commit a single file, it would be nice to have the option to auto-fill the 'scope' dialogue with the name of that file, relative to the root directory.\r\n\r\ne.g. if I were to do this:\r\n```\r\n// in root dir on a clean worktree\r\n$ touch some_dir/some.file\r\n$ git add .\r\n$ cz c\r\n```\r\n\r\nI would expect the `cz c` dialogue to pop-up, where I can choose fix/feat etc., then when I am asked 'What is the scope of this change?' I would expect the text input to be prefilled with `some.file`, so I can change it to something else, or just hit enter to continue.\r\n\r\nThis would not be applicable if a commit contains multiple files, as a file-based scope doesn't make sense there, so I would expect the scope field to be left blank in that case.\r\n\r\n### Possible Solution\r\n\r\nAdd a `boolean` option `prefill_scope_for_single_files` that defualts to `false` and when set to `true`, makes the CLI tool scan for the number of files that have changed upon asking the scope question.\r\n\r\nIf the number of files is one, grab the filename and pre-fill it as the scope.\r\n\r\nOptional: add `boolean` opt `prefill_scope_for_single_files_relative` that defaults to `false` and determines whether the scope should be prefilled with `some.file` (when opt is `false`) or `some_dir/some.file` (when opt is `true`)\r\n\r\n### Additional context\r\n\r\nThis would have to be an opt-in feature for sure as some people skip the scope step.","author":{"url":"https://github.com/codevogel","@type":"Person","name":"codevogel"},"datePublished":"2024-05-07T10:03:39.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/1099/commitizen/issues/1099"}