Opens profile photo
Follow
Click to Follow github
GitHub
@github
The complete developer platform to build, scale, and deliver secure software.
San Francisco, CAgithub.comBorn October 19Joined February 2008

GitHub’s Tweets

Need some inspo for the last 3 days of Hacktoberfest? Check out these open source projects who recently shipped major version releases, incl. , , OS, & more. What project are you working on? Drop links in comments 👇
7
104
The provided office hours for #OpenSource projects looking to reduce their risk of breach. One thing we learned? Adopting a few simple practices can significantly improve your project’s security. Read more of our observations here.
57
Open source is not just about code. Many projects welcome the following types of contributions: 📝 Documentation 🎨 Design 🧪 Testing 🌎 Translation Brian Douglas shows us how impactful code reviews and issue triage are to Open Sauced: youtu.be/BaIjOw1K5JY
Embedded video
0:50
9K views
4
151
Forks are confusing. What is a fork? How do fork permissions work? What are the security and permission implications? Based on feedback from developers, we've improved how forks work and added more details to our documentation. Check it out!
3
89
Actions changed how developers automate workflows with GitHub. We’re introducing a 🆕 navigation to manage your Actions experience, improving discoverability and accessibility, as well as opening up future feature opportunities.
5
140
Every project has a first commit and 15 years ago on this day, GitHub started that same way. From hosting git repos to the pull request, the contribution graph, Actions, Codespaces, and now Copilot, here’s to celebrating all the initial commits and iterating on them. 🚀
Embedded video
0:09
9K views
4
122
How can we write better developer documentation? 📝 Dan Jutan, a product manager at Astro, shared great advice about understanding your readers and their goals. Watch the full video for more: youtu.be/B1ejSMzr0n4
Embedded video
0:55
12.3K views
6
104
4️⃣ No surprises here--we value working in the open. Scalar was an open source project from day one, and was never intended to be a project only for internal use. So now we have a history of public code changes to talk about! 5/6
1
24
Show this thread
3️⃣ Making any kind of software change adds risk to a project. That risk is mitigated when we have a large set of battle-hardened tests. With a robust test suite available, we were able to make significant changes to our architecture with confidence.
1
19
Show this thread
2️⃣ Incremental changes > wholesale rewrites. We focused on small changes that solved an immediate need and optimized for reducing our technical debt and creating a better architecture. 3/6
1
23
Show this thread
1️⃣ Code speaks volumes. An architectural design on paper isn't enough for solving problems at scale. Before committing to a decision, we would quickly build a prototype and measure its performance. 📈 2/6
1
21
Show this thread
When you're faced with a BIG engineering effort, how do you approach development? Before we dove into code for contributing Scalar to Git, we solidified four 4️⃣ development principles that we used to guide our decisions. 🧵
Image
2
144
Show this thread