Skip to content

Comments

Gboards Consolidation#8262

Closed
germ wants to merge 4 commits intoqmk:masterfrom
germ:gboards-consolidate
Closed

Gboards Consolidation#8262
germ wants to merge 4 commits intoqmk:masterfrom
germ:gboards-consolidate

Conversation

@germ
Copy link
Contributor

@germ germ commented Feb 28, 2020

Updates all g Heavy industries boards to use new features and consolidate them in /keyboards/gboards/

Types of Changes

  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)

Issues Fixed or Closed by This PR

Requires #8120 to be merged

@drashna
Copy link
Member

drashna commented Mar 1, 2020

Just a heads up, because this touches so many files, this may take more time to review. A separate PR for each board may be easier and get merged in faster.

@germ
Copy link
Contributor Author

germ commented Mar 10, 2020

Yeah sorry about that, they all require the new combo stuff so rather then having 10PRs open and dependant on the userspace/engine stuff and #8120 this seemed like a good option. :(

Copy link

@micolous micolous left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a quick look at this trying to build for Ginny – it seems to build OK, but there are some issues (in the review comments).

I notice there's a lot of files here that have the execute bit set that don't need it (eg: keyboards/gboards/k/ginny/config.h, ginny.c, ginny.h, matrix.c, readme.md...)

@germ
Copy link
Contributor Author

germ commented Apr 6, 2020

Did the changes @micolous requested. Can we get another set of eyes on this @drashna

@germ germ closed this Apr 25, 2020
@germ germ force-pushed the gboards-consolidate branch from 88967a9 to 28e5969 Compare April 25, 2020 09:46
@germ germ reopened this Apr 25, 2020
Copy link
Member

@zvecr zvecr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im going to double down on the "needs separate PRs". As it stands, this PR relocates user keymaps which falls under our current breaking changes definition. Separate PRs allows us to merge your new keyboards now while working out what we can do for the existing boards.

@germ
Copy link
Contributor Author

germ commented Apr 26, 2020

Went ahead a broke it up into seperate PRs (referenced above). Closing this for the time being

@germ germ closed this Apr 26, 2020
@pirj pirj mentioned this pull request Sep 23, 2020
14 tasks
@pirj pirj mentioned this pull request May 28, 2021
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking_change Changes that need to wait for a version increment keyboard

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants