Github copilot metrics

[psmcbord]

Copilot Metrics

General

Body

How to truly calculate the percentage of code generated by copilot?
I am pulling the total repository lines added using github api and AI lines accepted from copilot metrics.

Lines of code accepted(Copilot metrics) / Lines of code Added from all commits (Github api)* 100.

I know this are some edge cases like what if the dev edited the lines of code accepted etc?

Is there a better way to calculate it?

[0xlengo]

Hi @fabio-luppi,

You can achieve automatic releases on push to main using GitHub Actions.

Here’s a basic example of a workflow that does this:

name: Release on Push to Main

on:
  push:
    branches:
      - main

jobs:
  release:
    runs-on: ubuntu-latest

    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Set up Node.js (if needed)
        uses: actions/setup-node@v4
        with:
          node-version: '20' # Optional, remove if not using Node

      - name: Create GitHub Release
        uses: softprops/action-gh-release@v2
        with:
          tag_name: v1.0.${{ github.run_number }}
          name: Release v1.0.${{ github.run_number }}
          body: |
            Automated release from main branch
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Notes:
This creates a new tag like v1.0.45 (based on the workflow run number).

You can customize the versioning, changelog, and tag name.

If you use semantic-release, you can replace softprops/action-gh-release with that.

Let me know if you're using a specific language or build system, happy to tailor this example.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[ashmeet07]

☁️ GitHub Codespaces vs. GitHub Actions: A Comparison

GitHub Codespaces and GitHub Actions are two powerful, but fundamentally different, cloud-based services provided by GitHub. They are designed to assist the developer workflow in separate stages.

Feature	GitHub Codespaces 🧑‍💻	GitHub Actions ⚙️
Primary Goal	Development / Coding / Debugging	Automation / CI/CD / Workflow
What it is	A Cloud-Hosted Development Environment based on a customizable container (devcontainer).	An Event-Driven Automation Engine that runs workflows.
Use Case	Writing, compiling, testing, and debugging code in a consistent, instantly available environment.	Building, testing, and deploying code automatically based on events (e.g., git push, Pull Request).
Lifecycle	Interactive & Long-Lived. You connect to it and use it until you stop or delete it.	Ephemeral & Job-Based. It spins up a runner, executes a workflow, and shuts down.
Trigger	Manual user action (e.g., clicking "Open in Codespaces") or a prebuild schedule.	Repository events (e.g., push, pull_request, issue_comment, schedule).

---

🎯 Key Differences in Function

• Codespaces is for Humans: It replaces your local development setup (your laptop, IDE, and dependencies). It is an interactive workspace that you connect to via a browser or desktop IDE (like VS Code) to write code.
• Actions is for Tasks: It replaces automation scripts and traditional CI/CD servers. It is a set of automated jobs that execute predefined steps on a server when a specific event occurs, with no human interaction required during the run.

🤝 How They Interact

Although their purposes differ, they often work together:

1. A developer uses a Codespace to write and test new features.
2. The developer commits and pushes the new code.
3. The git push event triggers a GitHub Action to automatically run the build, static analysis, and unit tests on the code that was just pushed.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬