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

add ergodox Community Layout for LAYOUT_ergodox keyboards #22963

Merged
merged 4 commits into from
Oct 7, 2024

Conversation

dunk2k
Copy link
Contributor

@dunk2k dunk2k commented Jan 26, 2024

Description

add ergodox Community Layout to keyboards with LAYOUT_ergodox layout. layout information must match respective Community Layout to qualify.

Types of Changes

  • Core
  • Bugfix
  • New feature
  • Enhancement/optimization
  • Keyboard (addition or update)
  • Keymap/layout/userspace (addition or update)
  • Documentation

Issues Fixed or Closed by This PR

  • n/a

Checklist

  • My code follows the code style of this project: C, Python
  • I have read the PR Checklist document and have made the appropriate changes.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Copy link

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

@github-actions github-actions bot added the stale Issues or pull requests that have become inactive without resolution. label Mar 12, 2024
@dunk2k
Copy link
Contributor Author

dunk2k commented Mar 12, 2024

please label as awaiting review

@github-actions github-actions bot removed the stale Issues or pull requests that have become inactive without resolution. label Mar 13, 2024
@dunk2k dunk2k changed the base branch from develop to master March 14, 2024 23:06
@dunk2k dunk2k changed the base branch from master to develop March 19, 2024 16:48
@dunk2k dunk2k changed the title amend ergodox Community Layout for LAYOUT_ergodox keyboards add ergodox Community Layout for LAYOUT_ergodox keyboards Apr 12, 2024
Copy link

github-actions bot commented Jun 7, 2024

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

@github-actions github-actions bot added the stale Issues or pull requests that have become inactive without resolution. label Jun 7, 2024
@dunk2k
Copy link
Contributor Author

dunk2k commented Jun 7, 2024

Please label as awaiting review

@github-actions github-actions bot removed the stale Issues or pull requests that have become inactive without resolution. label Jun 8, 2024
Copy link

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

@github-actions github-actions bot added the stale Issues or pull requests that have become inactive without resolution. label Jul 23, 2024
@dunk2k
Copy link
Contributor Author

dunk2k commented Jul 23, 2024

Please label as awaiting review

@github-actions github-actions bot removed the stale Issues or pull requests that have become inactive without resolution. label Jul 24, 2024
Copy link

Thank you for your contribution!
This pull request has been automatically marked as stale because it has not had activity in the last 45 days. It will be closed in 30 days if no further activity occurs. Please feel free to give a status update now, or re-open when it's ready.
For maintainers: Please label with bug, awaiting review, breaking_change, in progress, or on hold to prevent the issue from being re-flagged.

@github-actions github-actions bot added the stale Issues or pull requests that have become inactive without resolution. label Sep 18, 2024
@dunk2k
Copy link
Contributor Author

dunk2k commented Sep 18, 2024

please label as awaiting review

@github-actions github-actions bot removed the stale Issues or pull requests that have become inactive without resolution. label Sep 20, 2024
@tzarc tzarc merged commit c3ffbe4 into qmk:develop Oct 7, 2024
2 of 3 checks passed
@dunk2k dunk2k deleted the comm_ergodox branch October 7, 2024 06:46
ilham-agustiawan pushed a commit to ilham-agustiawan/qmk_firmware that referenced this pull request Nov 30, 2024
smallketchup82 pushed a commit to smallketchup82/qmk_firmware that referenced this pull request Dec 1, 2024
jlaptavi pushed a commit to jlaptavi/qmk_firmware that referenced this pull request Dec 3, 2024
DmNosachev pushed a commit to DmNosachev/qmk_firmware that referenced this pull request Dec 7, 2024
SyrupSplashin pushed a commit to SyrupSplashin/qmk_firmware that referenced this pull request Dec 10, 2024
LeonMusCoden pushed a commit to LeonMusCoden/qmk_firmware that referenced this pull request Jan 5, 2025
MichaelScofield45 pushed a commit to MichaelScofield45/qmk_firmware that referenced this pull request Jan 8, 2025
pashashocky pushed a commit to pashashocky/qmk that referenced this pull request Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants