What I learned opening my first sixty open source pull requests
The author shares insights from their experience of opening sixty open source pull requests after starting a new GitHub account. They emphasize the importance of checking for existing pull requests and reading project guidelines before submitting changes. Key lessons include understanding the significance of API stability and the value of exploring code beyond the issue tracker.
- ▪The author began with zero contributions on GitHub after creating a new account.
- ▪They encountered many existing pull requests for issues they attempted to address.
- ▪Reading the project's CONTRIBUTING.md and PR templates is crucial to avoid automatic rejections.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3936350) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Charlie Tonneslan Posted on May 17 • Originally published at c-tonneslan-portfolio.vercel.app What I learned opening my first sixty open source pull requests #beginners #opensource #career #github Twelve days ago my GitHub account had zero contributions on it. Not zero this year, zero ever, because I'd deleted my old account in a fit of housekeeping and started fresh from a new email.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
