Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update support for s6xty #2350

Merged
merged 3 commits into from
Oct 28, 2024
Merged

Update support for s6xty #2350

merged 3 commits into from
Oct 28, 2024

Conversation

trnthsn
Copy link

@trnthsn trnthsn commented Oct 9, 2024

Description

QMK Pull Request

QMK pull request

VIA Keymap Pull Request

VIA keymap pull request

Checklist

  • The VIA support for this keyboard is MERGED in QMK master already (MANDATORY)
  • VIA keymap is MERGED in VIA userspace master already (MANDATORY)
  • The VIA definition follows the guide here: https://caniusevia.com/docs/layouts
  • I have a V3 JSON version for this keyboard definition.(MANDATORY)
  • I have formatted the JSON file to have consistent formatting with the rest of the repository.
  • I have tested this keyboard definition using VIA's "Design" tab.
  • I have tested this keyboard definition with firmware on a device.
  • I have assigned alpha keys and modifier keys with the correct colors.
  • The Vendor ID is not 0xFEED

@Cipulot Cipulot added the pending VIA keymap merge Waiting for merge into VIA keymap label Oct 14, 2024
@Cipulot
Copy link
Collaborator

Cipulot commented Oct 14, 2024

On hold till QMK merge, then subsequent via keymap merge.

@Cipulot
Copy link
Collaborator

Cipulot commented Oct 14, 2024

File name could also be changed from trnthsn_s6xty_via.json to s6xty.json.

v3/trnthsn/s6xty/trnthsn_s6xty_via.json Outdated Show resolved Hide resolved
@Cipulot Cipulot merged commit a4d5499 into the-via:master Oct 28, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending VIA keymap merge Waiting for merge into VIA keymap
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants