Skip to content

Conversation

@saumyashahi
Copy link
Contributor

This commit updates the blog post frontmatter to correctly reference the author file:

  • Changed author from saumyashahi.md to saumya-shahi.md to match the actual path.
  • Ensures the author metadata renders properly on the GSoC blog post page.

Tested locally and verified metadata displays as expected.

@github-actions
Copy link

🎉 All Checks Passed!

Status: ✅ Ready to merge

✅ Completed Workflows

Workflow Status Details
🔨 Continuous Integration ✅ Passed Build completed successfully
📝 Code Linting ✅ Passed All formatting and style checks passed

🚀 This PR is ready for review and can be safely merged to main branch!

Great work! Your code meets all quality standards. 👏

@pikurasa
Copy link
Contributor

@saumyashahi For the future, please, please, please create a new branch to work in.

This helps everybody out, as it avoids conflicts.

There are many ways to do this. What I use is:

Before working on something new, I run: git checkout -b NEWBRANCHNAME

If you accidentally start working on something in the main branch, there's different ways to navigate into a new branch, such as stashing your work, creating the new branch, and "popping" it back in.

@pikurasa pikurasa merged commit 0daa226 into sugarlabs:main Jun 18, 2025
3 checks passed
@saumyashahi
Copy link
Contributor Author

@saumyashahi For the future, please, please, please create a new branch to work in.

This helps everybody out, as it avoids conflicts.

There are many ways to do this. What I use is:

Before working on something new, I run: git checkout -b NEWBRANCHNAME

If you accidentally start working on something in the main branch, there's different ways to navigate into a new branch, such as stashing your work, creating the new branch, and "popping" it back in.

Yes I will do that in further PRs, it was a one liner change so I thought it is fine to do it from the main itself.

@pikurasa
Copy link
Contributor

Yes I will do that in further PRs, it was a one liner change so I thought it is fine to do it from the main itself.

It can get very messy, even for things that otherwise seem "small" and "trivial". I recommend getting in the habit of creating new branches by default.

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.

2 participants