GitHub中Build and Passing按钮：定义、添加方法、优势及费用咨询

Hey there! Let's break down all your questions about that "Build: Passing" badge you've seen on GitHub repositories:

That little badge is a status indicator tied to GitHub's automation tools (most commonly GitHub Actions, though historically it was used with external services like Travis CI). It shows at a glance whether your project's automated workflows—like building the code, running tests, or linting—completed successfully. If the badge says "Passing", your latest code changes didn't break the core workflow; if it's "Failed", there's an issue that needs fixing. It's like a quick health check for your repo.

Adding it is straightforward, and it starts with setting up an automated workflow first:

• Step 1: Create your workflow configuration
  In your repo, make a new directory called .github/workflows, then add a YAML file (e.g., ci.yml) inside it. This file defines your automation steps—for example, a Node.js project might include installing dependencies with npm install and running tests with npm test. GitHub has pre-built templates for most languages/frameworks to make this easier.
• Step 2: Generate the badge link
  Go to your repo's "Actions" tab, find the workflow you just created, click the three dots in the top-right corner of the workflow, and select "Create status badge". GitHub will generate a Markdown snippet for you—copy that.
• Step 3: Add it to your README
  Paste the copied Markdown into your README.md file (usually at the top, so visitors see it first). Commit and push the changes, and the badge will show up with the current status of your workflow.

• Instant credibility for visitors: Anyone checking out your repo can immediately see that your code is tested and builds successfully—no need to dig through workflow logs. This is especially helpful for open-source projects looking to attract users or contributors.
• Quick feedback for contributors: When someone submits a pull request, the badge will update to reflect if their changes broke the workflow. This lets contributors catch issues early, without waiting for manual reviews.
• Visual workflow tracking: Instead of navigating to the Actions tab every time, you can see the workflow status right on the repo's main page. It's a time-saver for maintaining the project.
• Builds trust with users: A passing badge signals that the project is actively maintained and has quality checks in place, making users more likely to rely on it.

Great question!

• For public repositories: GitHub Actions (and the status badges that come with it) are completely free. You can run unlimited workflows and display the badge without any cost.
• For private repositories: GitHub gives you a monthly free tier of workflow minutes (the exact amount depends on your plan). Once you exceed that tier, you'll pay for additional minutes—but the status badge itself doesn't incur any extra charges. As long as your workflow is running (even on paid minutes), the badge will work as expected.

内容的提问来源于stack exchange，提问作者alhelal