Fixing Issue #4222: Add `automation.yml` Workflow

Hey guys! Today, we're diving into fixing issue #4222 by adding a functional automation.yml workflow. This is a crucial step in automating tasks within your repository, and I'm going to walk you through each step to make sure you get it right. Let's get started!

1. Open the Workflow File

First things first, you need to access the workflow file in your repository. This file is where the magic happens, defining the automated processes you want to run. You can open it using your favorite code editor. Here’s the command you can use in your terminal:

code .github/workflows/automation.yml   # or any editor you prefer

This command will open the automation.yml file located in the .github/workflows/ directory. If the file doesn't exist yet, don't worry; your editor will likely create it for you. Make sure you're in the root directory of your Git repository when you run this command. If you prefer using a different editor, just replace code with the appropriate command or open the file manually through your editor's interface.

Ensure you have the necessary permissions to modify files in the repository. If you're working on a team project, you might need to fork the repository and create a pull request with your changes. This step is essential because the automation.yml file dictates how your repository responds to certain events, such as labeling issues. A correctly configured workflow can save you a lot of time and effort by automating repetitive tasks. For instance, you can automatically create issues, assign labels, or even deploy your code. In our case, we’re setting up a workflow that automatically creates a “core-features” issue when a specific label is applied. So, let's get that file open and ready for some action!

2. Replace Placeholder Content with Functional Workflow

Now that you have the automation.yml file open, it’s time to fill it with the code that will drive our automation. We're going to replace any placeholder content with a minimal, functional workflow that does exactly what we need. This workflow will run on the issues labeled event, which means it will trigger whenever an issue is labeled. It will then check if the label is automation and, if so, create a “core-features” issue using actions/github-script.

Here’s the YAML code you need to paste into your automation.yml file:

name: Automation – create core‑features issue

on:
  issues:
    types: [labeled]

jobs:
  create-core-features-issue:
    if: github.event.label.name == 'automation'
    runs-on: ubuntu-latest
    steps:
      - name: Create core‑features issue
        uses: actions/github-script@v7
        with:
          script: |
            const { owner, repo } = context.repo;
            const title = 'core‑features';
            const body = 'Automatically generated core‑features issue.';
            const existing = await github.rest.issues.listForRepo({
              owner,
              repo,
              state: 'open',
              labels: title
            });
            if (existing.data.length === 0) {
              await github.rest.issues.create({
                owner,
                repo,
                title,
                body,
                labels: [title]
              });
              console.log('✅ core‑features issue created');
            } else {
              console.log('ℹ️ core‑features issue already exists');
            }

Let’s break down what this code does. The name field gives your workflow a friendly title. The on section specifies the trigger—in this case, labeling an issue. The jobs section defines the tasks that will run. We have one job here, create-core-features-issue, which only runs if the label name is automation. Inside the job, we use actions/github-script to run a JavaScript script. This script checks if an issue with the title “core-features” already exists. If not, it creates a new one with the specified title, body, and label. This ensures that you don't end up with duplicate issues and that your issue tracker stays organized.

Copy and paste this code carefully to avoid any typos or syntax errors. YAML is quite sensitive to indentation, so make sure the spacing is correct. Once you've pasted the code, save the file. We're one step closer to automating issue creation in your repository! This workflow provides a solid foundation, and you can always customize it further to fit your specific needs.

3. Commit & Push

Alright, you've got the workflow code in place, and now it's time to make it a permanent part of your repository. This involves committing the changes and pushing them to your remote repository. Think of it as saving your work and then sharing it with the world (or your team, at least!).

Here are the commands you'll need to run in your terminal:

git add .github/workflows/automation.yml
git commit -m "Add automation workflow to create core‑features issue"
git push

Let's break down each command:

• git add .github/workflows/automation.yml: This command stages the automation.yml file for commit. Staging is like preparing the file to be included in your next snapshot of changes. You're telling Git,