#GitHubAPI
GitHub's tidying up their API again. They're removing the code_scanning_upload field from the rate_limit endpoint. Always something shifting under the hood, gotta keep those integrations up to date! 😬 #GitHubAPI #DevOps
May 19, 2026 at 11:16 AM
Blogged: [HOWTO] Identify and remind inactive GitHub Copilot users

#github #githubcopilot #githubapi #githubactions
[HOWTO] Identify and remind inactive GitHub Copilot users
The author sought a method to identify inactive GitHub Copilot Business license users. After troubleshooting errors, they successfully implemented a reminder workflow and contributed improvements.
blog.rufer.be
February 20, 2025 at 7:21 AM
GitHub’s GraphQL Explorer is packing its bags—disappearing from the docs on Nov 7, 2025. Time to fire up your favorite client and keep the queries rolling. Want the full scoop? Read more in the blog. #GraphQL #GitHubAPI

🔗 https://news.google.com/rss/articles/CBMirAFBVV95cUxOaUtDQ25tNjY2bmktNU54N...
GraphQL Explorer removal from API documentation on November 7, 2025 - The Git...
news.google.com
May 23, 2026 at 10:25 PM
Heads up, GitHub API users! They're deprecating the code_scanning_upload field from the rate_limit endpoint. If your tooling relies on that, you've got until May 2026 to update. Future planning for the win! 🤓 #GitHubAPI #DevLife
May 5, 2026 at 9:16 PM
CI判定スクリプト、「GitHubの情報をちょっと取ってくるだけ」のつもりが認証・ページネーション・レート制限の沼にハマった話。

REST APIは権限のないPRにも404を返すため、「存在しない」のか「見せてもらえない」のか区別がつきません。gh CLIとの比較まとめました。

https://www.playpark.co.jp/blog/gh-cli-rest-api-comparison?utm_source=bluesky&utm_medium=social&utm_campaign=gh-cli-rest-api-comparison

#GitHubAPI #ghCLI
gh CLIとGitHub REST API、CI判定スクリプトではどちらを使うべきか比較する | ブログ | playpark
GitHub の自動判定をスクリプトで実装する際、gh と REST API のどちらを選ぶ?実装で陥りやすい認証・ページネーション・レート制限の落とし穴を学ぶことで、プロジェクトに最適な選択ができるようになります。
www.playpark.co.jp
August 25, 2026 at 6:50 PM
CI判定スクリプト、「GitHubの情報をちょっと取ってくるだけ」のつもりが認証・ページネーション・レート制限の沼にハマった話。

REST APIは権限のないPRにも404を返すため、「存在しない」のか「見せてもらえない」のか区別がつきません。gh CLIとの比較まとめました。

https://www.playpark.co.jp/blog/gh-cli-rest-api-comparison?utm_source=bluesky&utm_medium=social&utm_campaign=gh-cli-rest-api-comparison

#GitHubAPI #ghCLI
gh CLIとGitHub REST API、CI判定スクリプトではどちらを使うべきか比較する | ブログ | playpark
GitHub の自動判定をスクリプトで実装する際、gh と REST API のどちらを選ぶ?実装で陥りやすい認証・ページネーション・レート制限の落とし穴を学ぶことで、プロジェクトに最適な選択ができるようになります。
www.playpark.co.jp
August 24, 2026 at 6:49 PM
Outreach con IA: 68% de apertura y 23% de reply

Cómo un agente de outreach personalizado con IA logró 68% de apertura y 23% de reply enriqueciendo GitHub y clasificando objeciones con LLM. El playbook...

#outreachconia #hiperpersonalizacion #githubapi #llama2 #emailmarketing
Outreach con IA: 68% de apertura y 23% de reply
Enriquecimiento de GitHub, clasificación de objeciones con LLM y A/B testing bayesiano: el playbook técnico de un agente de outreach que generó USD 2,1M.
blog.donweb.com
August 28, 2026 at 4:25 AM
CI判定スクリプト、「GitHubの情報をちょっと取ってくるだけ」のつもりが認証・ページネーション・レート制限の沼にハマった話。

REST APIは権限のないPRにも404を返すため、「存在しない」のか「見せてもらえない」のか区別がつきません。gh CLIとの比較まとめました。

https://www.playpark.co.jp/blog/gh-cli-rest-api-comparison?utm_source=bluesky&utm_medium=social&utm_campaign=gh-cli-rest-api-comparison

#GitHubAPI #ghCLI
gh CLIとGitHub REST API、CI判定スクリプトではどちらを使うべきか比較する | ブログ | playpark
GitHub の自動判定をスクリプトで実装する際、gh と REST API のどちらを選ぶ?実装で陥りやすい認証・ページネーション・レート制限の落とし穴を学ぶことで、プロジェクトに最適な選択ができるようになります。
www.playpark.co.jp
August 26, 2026 at 10:32 PM
Ghost GitHub accounts, leaked tokens, and fake scanners are being used to map orgs, repos, and users over months. Some campaigns progressed from recon to repo cloning and data theft. #GitHubAPI #Datadog #Leakage
Ghost Accounts Abuse GitHub API in Mass Recon Campaign
Threat actors are abusing the GitHub API with dormant ghost accounts, leaked credentials, and automated scanners to enumerate organizations, repositories, and user accounts over several months. In some cases, the activity escalated from reconnaissance to cloning repositories and exfiltrating data from targeted organizations. #GitHubAPI #Datadog...
www.hendryadrian.com
July 11, 2026 at 9:15 PM
Datadog Uncovers Coordinated GitHub API Campaigns Targeting Organizations for Large-Scale Reconnaissance #CyberFraud #DatadogSecurityLabs #GitHubAPI
Datadog Uncovers Coordinated GitHub API Campaigns Targeting Organizations for Large-Scale Reconnaissance
  Datadog Security Labs has identified multiple coordinated campaigns that are systematically using the GitHub API to enumerate corporate GitHub organizations, repositories, and user accounts. The activity highlights how attackers are leveraging both legitimate and compromised resources to gather intelligence on organizations while blending into normal API traffic. "Operators rely on automated scraping tooling with custom or legitimate-sounding user agents, leveraging GitHub 'ghost' accounts that are often years old, or compromised OAuth tokens and personal access tokens (PATs) from legitimate users," Julie Agnes Sparks, senior security engineer at Datadog, said. According to the security researchers, the majority of the observed activity has focused on collecting publicly available information. However, in a limited number of incidents, the attackers progressed beyond reconnaissance and successfully cloned private repositories. The campaigns rely on a combination of automated scanning tools, more than 50 dormant GitHub accounts, and several legitimate accounts whose personal access tokens (PATs) had either been unintentionally exposed or compromised. These resources are used to perform extensive enumeration across multiple GitHub organizations. A notable aspect of the operation is the use of so-called "ghost" accounts that were created between two and five years ago and deliberately left inactive before being activated for API-based reconnaissance. By using aged accounts instead of newly created ones, the attackers are able to make their activity appear more legitimate and reduce the likelihood of triggering security alerts. Since a significant portion of GitHub's API can be accessed without authentication, the attackers are able to retrieve large amounts of publicly available data while remaining indistinguishable from routine API traffic. Their reconnaissance includes listing public repositories within organizations, mapping user followers and following relationships, identifying gists, starred repositories, and organization memberships, as well as executing GraphQL queries against public objects. The collected information enables threat actors to build detailed profiles of an organization's GitHub environment, including its public repositories, contributors, developer relationships, and project activity. Such intelligence can be used to support future targeted attacks. Datadog also confirmed that in a small number of cases, attackers escalated their activity by cloning a private repository belonging to a targeted organization, indicating that the campaigns can extend beyond information gathering. "Individually, most of these requests are unremarkable. They hit public endpoints, authenticate cleanly or not at all, and return successful responses," Datadog said. "The concern lies in the aggregate: a group of accounts moving in sync across companies' GitHub organizations with versioned custom tooling iterating over weeks, and in the worst case, actors that stopped enumerating and started cloning."
dlvr.it
July 11, 2026 at 7:55 PM
Dormant GitHub accounts and stolen tokens are helping attackers blend in while using the GitHub API to map orgs, repos, and users. Some campaigns even cloned a private repo. #GitHubAPI #GhostAccounts #OAuthTokens
Dormant GitHub Accounts Help Attackers Blend In While Mapping Corporate Orgs
Datadog Security Labs says multiple overlapping campaigns are using the GitHub API to systematically enumerate organizations, repositories, and user accounts, often with dormant "ghost" accounts or compromised tokens. In some cases, the activity moved beyond public data collection and included cloning a private repository, making the coordinated scraping effort more concerning....
www.hendryadrian.com
July 10, 2026 at 1:30 AM
My #salesforce1selfie: app showing how to call external APIs, e.g. get issues from @GitHubAPI #s1devweek
November 14, 2024 at 4:17 AM
Check out the new Azure DevOps extension simplifying JWT generation & token management for streamlined GitHub API calls in Azure Pipelines. #AzureDevOps #GitHubAPI https://github.blog/enterprise-software/ci-cd/how-to-streamline-github-api-calls-in-azure-pipelines/
How to streamline GitHub API calls in Azure Pipelines
Build a custom Azure DevOps extension that eliminates the complexity of JWT generation and token management, enabling automation and security controls.
github.blog
August 5, 2025 at 8:33 PM
"Just landed a big refactor for our GitHub API integration. Made a ton of changes to task linking, PR status and issue creation. Still shaking off the code dust from the rebuild - fingers crossed everything is stable now #GitHubAPI #DevLife"
March 4, 2026 at 4:13 AM
Blogged: Creating GitHub pull requests from the command-line with Hub https://t.co/6QLVw7DrcN @github @GitHubAPI #AspNetCore
January 23, 2018 at 5:20 PM
We urge our engineering leaders to eliminate busywork by automating the tracking of engineering metrics. As a side effect, they also keep their software skills sharp.

https://victoronsoftware.com/posts/track-engineering-metrics/
#EngineeringManagement #GitHubAPI #GoogleAPIs #GitHubActions #Golang
How to easily track engineering metrics
How to automate tracking of engineering metrics and display them in Google office suite
victoronsoftware.com
December 27, 2024 at 1:03 PM
movee.jp/member
moveeのメンバーページはGithubAPIを活用してメンバーのGithubデータを表示しています。
少なからず、パブリックリポジトリの活動が見えます。
株式会社movee/メンバー
movee.jp
March 12, 2024 at 10:36 PM
Okey so beyond Todo app to be built on top of @GitHubAPI projects beta where is the zulip inspired chat app built ontop of GitHub discussions ?

Categories = streams
Title = topic
Threads per topic
Can subscribe/unsubscribe has labels for additional classification...
November 17, 2024 at 1:52 AM
I've been fascinated with API based applications. Being able to query multiple endpoints, fetch data and display results in the UI kept me looking. I finally created my own API app that queries the githubAPI and displays results. #50projectsin50days. #onepercentimprovement
Fetch and Display Github profiles using Axios
buff.ly
January 26, 2025 at 3:30 AM
A sneak peek at some exciting open source community management features in the pipeline at @GitHub... https://developer.github.com/v3/repos/community/ https://twitter.com/GitHubAPI/status/830146590715297793
REST API endpoints for community metrics - GitHub Docs
developer.github.com
November 16, 2024 at 2:10 AM
A sneak peek at some exciting open source community management features in the pipeline at @GitHub... https://developer.github.com/v3/repos/community/ https://twitter.com/GitHubAPI/status/830146590715297793
REST API endpoints for community metrics - GitHub Docs
developer.github.com
November 16, 2024 at 2:10 AM
🐚 I wrote a little command line tool for fetching auto-paginated and auto-authenticated @GitHubAPI content.

https://github.com/zeke/ghurl
GitHub - github-modules/ghurl: A CLI for fetching data st...
A CLI for fetching data straight from the GitHub API - gi...
github.com
February 23, 2025 at 4:28 PM