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

Use correct separator in keywords.txt #1008

Merged
merged 1 commit into from
Dec 6, 2017
Merged

Use correct separator in keywords.txt #1008

merged 1 commit into from
Dec 6, 2017

Conversation

per1234
Copy link
Contributor

@per1234 per1234 commented Dec 2, 2017

The Arduino IDE currently requires the use of a tab separator between the name and identifier. Without this tab the keyword is not highlighted.

Reference: https://github.com/arduino/Arduino/wiki/Arduino-IDE-1.5:-Library-specification#keywords

@fallberg
Copy link
Contributor

fallberg commented Dec 6, 2017

If you insist on having hyperlinks in the commit message, I suggest you use a URL-shorterner for them.
Having a line broken URL is kind of pointless since it is not "working".

The Arduino IDE currently requires the use of a tab separator between
the name and identifier. Without this tab the keyword is not
highlighted.
@per1234
Copy link
Contributor Author

per1234 commented Dec 6, 2017

Commit line length issue that was breaking the gitler test fixed.
URL removed from commit message.

I recommend adding the commit message requirements to CONTRIBUTING.md.

@fallberg
Copy link
Contributor

fallberg commented Dec 6, 2017

Good point. @henrikekblad will you look into that? The code contribution guidelines are also available here.

@tekka007 tekka007 merged commit 6337b8b into mysensors:development Dec 6, 2017
mfalkvidd added a commit to mfalkvidd/MySensors that referenced this pull request Dec 8, 2017
As mentioned by per1234 in
mysensors#1008
we should make it easier to find the full code contribution
guidelines.

Since we have multiple git repos, we don't want to duplicate the
guidelines in each repo. Instead, we link to the canonical source
on mysensors.org.
fallberg pushed a commit that referenced this pull request Dec 9, 2017
As mentioned by per1234 in
#1008
we should make it easier to find the full code contribution
guidelines.

Since we have multiple git repos, we don't want to duplicate the
guidelines in each repo. Instead, we link to the canonical source
on mysensors.org.
@tekka007 tekka007 added this to the 2.2.0 milestone Jan 23, 2018
mfalkvidd added a commit to mfalkvidd/MySensors that referenced this pull request Feb 18, 2018
…-inclusionfix

* origin/development: (31 commits)
  Development version 2.2.1-alpha (mysensors#1043)
  MySensors 2.2.0 release
  Update README.md for upcoming release (mysensors#994)
  Add MY_INCLUSION_LED_PIN (mysensors#1030)
  Relax Gitler on commit headline length (mysensors#1031)
  Correct misspells (mysensors#1028)
  SignalReport disabled by default (mysensors#1027)
  Linux/SerialPort: Log success message (mysensors#1021)
  Linux: Fix null ptr exception (mysensors#1025)
  Update doxygen (mysensors#1024)
  Doxygenize MyGatewayTransport (mysensors#1023)
  RFM69: Fix compiler warnings (mysensors#1020)
  Add MY_RS485_SOH_COUNT option (mysensors#1014)
  Update reference to Code Contribution Guidelines (mysensors#1011)
  MySensors 2.2.0-rc.2 (mysensors#1000)
  Use correct separator in keywords.txt (mysensors#1008)
  Fix FOTA updates with smart sleep (mysensors#999)
  Harmonize debug outputs (mysensors#1002)
  Add MY_DEBUGDEVICE to redirect debug output (mysensors#1006)
  MySensors 2.1.1 release (mysensors#752)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants