Upload blog for GitHub Universe 2024 #35817
Conversation
✅ Deploy Preview for home-assistant-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
source/_posts/2024-11-18-event-wrapup-github-universe-24.markdown
Outdated
Show resolved
Hide resolved
source/_posts/2024-11-18-event-wrapup-github-universe-24.markdown
Outdated
Show resolved
Hide resolved
source/_posts/2024-11-18-event-wrapup-github-universe-24.markdown
Outdated
Show resolved
Hide resolved
Thanks for those @frenck Co-authored-by: Franck Nijhof <frenck@frenck.nl>
📝 WalkthroughWalkthroughThe changes involve two primary updates: the addition of a new entry for "Missy Quarry" in the Changes
Sequence Diagram(s)sequenceDiagram
participant Author as Missy Quarry
participant Community as Home Assistant Community
participant Event as GitHub Universe '24
Author->>Event: Attends event
Author->>Community: Coordinates community meetup
Community->>Event: Engages at the booth
Author->>Community: Shares experiences and achievements
Author->>Event: Reflects on community engagement
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (3)
source/_data/people.yml (1)
91-91: Add newline at end of fileAdd a newline character at the end of the file to follow YAML best practices and make the file more git-friendly.
github: missyquarry +🧰 Tools
🪛 yamllint
[error] 91-91: no new line character at the end of file
(new-line-at-end-of-file)
source/_posts/2024-11-18-event-wrapup-github-universe-24.markdown (2)
13-13: Enhance image accessibilityWhile all images have alt text, some could be more descriptive for better accessibility.
Consider these improvements:
- Line 13: Add more context to alt text, e.g., "GitHub Universe 2024 Event Wrap-up banner"
- Line 48: Enhance alt text to "Home Assistant ranked as number one open source project on GitHub"
- Line 52: Add context to alt text, e.g., "Graph showing top five projects by contributors from GitHub Octoverse 2024 report"
Also applies to: 36-36, 40-40, 44-44, 48-48, 52-52, 56-56, 64-64, 70-70, 74-74, 78-78
46-46: Style and formatting improvementsA few minor suggestions to enhance readability and maintain documentation standards:
- Remove exclamation mark from heading "We are number 1!" to follow heading standards
- Add hyphens to compound adjectives:
-#1 open source project +#1 open-source project
- Consider replacing informal "y'all" with "our community" or "our users" for consistency with documentation style
Also applies to: 66-66
🧰 Tools
🪛 Markdownlint
46-46: Punctuation: '!'
Trailing punctuation in heading(MD026, no-trailing-punctuation)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
⛔ Files ignored due to path filters (10)
source/images/blog/2024-11-universe/art.jpgis excluded by!**/*.jpgsource/images/blog/2024-11-universe/booth.jpgis excluded by!**/*.jpgsource/images/blog/2024-11-universe/day-1-keynote.jpgis excluded by!**/*.jpgsource/images/blog/2024-11-universe/ha-keynote.jpgis excluded by!**/*.jpgsource/images/blog/2024-11-universe/meetup-audience.jpgis excluded by!**/*.jpgsource/images/blog/2024-11-universe/number-1.pngis excluded by!**/*.pngsource/images/blog/2024-11-universe/octoverse-contributors.pngis excluded by!**/*.pngsource/images/blog/2024-11-universe/postcard-badge.pngis excluded by!**/*.pngsource/images/blog/2024-11-universe/shiny.pngis excluded by!**/*.pngsource/images/blog/2024-11-universe/wonderfully-welcoming.pngis excluded by!**/*.png
📒 Files selected for processing (2)
source/_data/people.yml(1 hunks)source/_posts/2024-11-18-event-wrapup-github-universe-24.markdown(1 hunks)
🧰 Additional context used
🪛 yamllint
source/_data/people.yml
[error] 91-91: no new line character at the end of file
(new-line-at-end-of-file)
🪛 LanguageTool
source/_posts/2024-11-18-event-wrapup-github-universe-24.markdown
[style] ~15-~15: Consider using an extreme adjective for ‘big’.
Context: ... community growing, and there were some really big moments---our community meetup in San F...
(EXTREME_ADJECTIVES)
[uncategorized] ~17-~17: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...f being in 2nd place, we are now the #1 open source project on GitHub with over 21,000 cont...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~30-~30: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...was this my first event as a part of an open source project, but it was also my first time ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~42-~42: Consider an alternative to strengthen your wording.
Context: ...k questions from the community members. It was great talking to everyone who attended - bein...
(NICE_MEETING_YOU)
[uncategorized] ~50-~50: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...d announce something new: we are the #1 open source project on GitHub by active contributor...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~50-~50: Consider using an extreme adjective for ‘interesting’.
Context: .../octoverse/octoverse-2024/), which is a really interesting read. <img src='/images/blog/2024-11-u...
(EXTREME_ADJECTIVES)
[style] ~54-~54: Consider a different adjective to strengthen your wording.
Context: ...se 2024 report"> Our friends at GitHub did a great job of making sure we were surprised by thi...
(DO_A_GREAT_JOB)
[uncategorized] ~66-~66: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ... Day 1 is when we had our booth in the [Open Source Zone](https://github.blog/open-source/1...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[uncategorized] ~66-~66: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...-ching! How to attract funding for your open source projects](https://reg.githubuniverse.co...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~66-~66: The phrase ‘y’all’ is informal.
Context: ...story since Home Assistant is funded by y'all - the community - through our [Home Ass...
(Y_ALL)
[uncategorized] ~66-~66: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...ns with several people working on other open source projects like Homebrew and Ladybird. O...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
[style] ~76-~76: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...u going to build?
(AWESOME)
[style] ~84-~84: Consider using a more formal and expressive alternative to ‘amazing’.
Context: ...# Connecting with the community It was an amazing event, and so nice to meet my colleague...
(AWESOME)
[uncategorized] ~86-~86: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...continuously growing - becoming the top open source project on the platform. The next time ...
(EN_COMPOUND_ADJECTIVE_INTERNAL)
🪛 Markdownlint
source/_posts/2024-11-18-event-wrapup-github-universe-24.markdown
46-46: Punctuation: '!'
Trailing punctuation in heading
(MD026, no-trailing-punctuation)
🔇 Additional comments (4)
source/_data/people.yml (2)
87-88: LGTM! Proper spacing added
The added newline improves readability and maintains consistent formatting with other entries.
89-91: LGTM! Verify GitHub handle
The new entry follows the established format correctly.
✅ Verification successful
GitHub handle verified and confirmed
The GitHub handle missyquarry exists and matches the user's profile at Nabu Casa, confirming the correctness of the entry in people.yml.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Verify that the GitHub handle exists and is correctly spelled
gh api users/missyquarry > /dev/null
Length of output: 26
Script:
#!/bin/bash
# Let's try to get more information about the GitHub user
gh api users/missyquarry || echo "User not found"
# Also try with different casing since GitHub handles are case-insensitive
gh api users/MissyQuarry || echo "User not found"
Length of output: 2674
🧰 Tools
🪛 yamllint
[error] 91-91: no new line character at the end of file
(new-line-at-end-of-file)
source/_posts/2024-11-18-event-wrapup-github-universe-24.markdown (2)
1-11: Front matter looks good!
All required metadata fields are present and properly formatted.
19-24: Verify external link accessibility
The table of contents structure is good. Let's ensure all external links are accessible.
✅ Verification successful
External links and table of contents structure verified successfully
All external URLs in the blog post return HTTP 200 status codes, confirming they are accessible. The table of contents structure correctly matches the section headers with proper markdown anchor link syntax.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Description: Verify external links in the blog post
# Test: Check if external URLs are accessible
# Extract and test URLs
urls=(
"https://githubuniverse.com/"
"https://github.blog/open-source/10-projects-in-the-open-source-zone-at-github-universe-2024/"
"https://reg.githubuniverse.com/flow/github/universe24/attendee-portal/page/sessioncatalog/session/1715376172449001OEqW"
"https://github.blog/news-insights/octoverse/octoverse-2024/"
)
for url in "${urls[@]}"; do
echo "Testing: $url"
curl -sL -w "%{http_code}\n" "$url" -o /dev/null
done
Length of output: 1620
Proposed change
Type of change
currentbranch).currentbranch).nextbranch).nextbranch).Additional information
Checklist
currentbranch.nextbranch.Summary by CodeRabbit
New Features
Updates