Qmk_firmware: qmk compile could be context sensitive about keyboard directory

[yanfali]

Idea is: you are in keyboards/keebio/iris/rev3 and you type qmk compile if no defaults are set it detects the directory you are in and compiles that with the default keymap. If you have a default keymap set in your global config it attempts to compile your personal keymap if it exists.

This would make the qmk compile context sensitive to where it is being run from to source parameters for keyboard and keymap.

Feature Request Type

• [ ] Core functionality
• [ ] Add-on hardware support (eg. audio, RGB, OLED screen, etc.)
• [x] Alteration (enhancement/optimization) of existing feature(s)
• [ ] New behavior

Description

Think of these as fall back sources for parameters when there are none supplied by the defaults or the cli.

[skullydazed]

I think a good argument could be made for CWD overriding configuration. It would be consistent with how the global CLI operates- configuration can specify the default qmk_firmware location but your current directory will override that configuration.

[cfbender]

I'd love to take this one for hacktoberfest if that's alright! I think I should be able to do it, thought it will be some of the first python I've written for a bit. If you'd prefer someone more experienced I'd understand!

[thiagoyeds]

This would be very interesting for users who use it, leaving the complexity to QMK.

[stale[bot]]

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.