Skip to content

task/2549 create copilot-instructions.md and update branch/hook support for copilot agents#2550

Merged
JoernBerkefeld merged 3 commits intodevelopfrom
copilot/copilottask1234-create-copilot-instructions-md
Mar 15, 2026
Merged

task/2549 create copilot-instructions.md and update branch/hook support for copilot agents#2550
JoernBerkefeld merged 3 commits intodevelopfrom
copilot/copilottask1234-create-copilot-instructions-md

Conversation

Copy link
Contributor

Copilot AI commented Mar 15, 2026

Adds .github/copilot-instructions.md to standardize how GitHub Copilot agents interact with this repo — covering commit format, branch naming, PR creation, label assignment, and milestone linking. Extends two existing configs to recognize copilot/-prefixed branches.

Changes

  • .github/copilot-instructions.md (new) — instructs Copilot to:

    • Prefix commits with #<issue-number>: (compatible with commit-msg hook)
    • Name branches as copilot/<type>/<issue-number>-<issue-title> where type is task, bug, or feature
    • Title PRs as <type>/<issue-number> <issue title>
    • Use PULL_REQUEST_TEMPLATE.md structure with closes #<issue-number>
    • Assign c/<classname> labels for changed files in lib/metadataTypes/
    • Mirror the issue's milestone on the PR
  • .github/pr-labeler.yml — adds copilot/feature/*, copilot/bug/*, copilot/task/* alongside existing patterns

  • .husky/post-checkout — extends ticket ID extraction regex to match copilot/<type>/<id>-... branches while preserving all prior behavior:

    - '^((feature|bug|bugfix|fix|hotfix|task|chore)\/)?\K\d{1,7}'
    + '^((copilot\/)?(feature|bug|bugfix|fix|hotfix|task|chore)\/)?\K\d{1,7}'

Release details

Checklist

Before merge

  • Wiki updated with info in ticket listed under Documentation
  • ran npm run prepare-release (which runs npm audit fix, npm run lint-ts, npm run lint:fix, git add, git commit)
  • pushed potential changes made by prepare-release

After merge

  • merged all dependabot PRs that target main branch
  • updated bug template to include the new version
  • updated .mcdevrc for tests to the new version
  • ran npm run version:major/minor/patch
  • pushed version-prep commits
  • merged main branch into develop branch
  • closed GitHub milestone
  • created new GitHub Release

Documentation

No documentation changes required.

Issues

Original prompt

This section details on the original issue you should resolve

<issue_title>[TASK] create copilot-instructions.md</issue_title>
<issue_description>Create a copilot-instructions.md file in the .github directory for this project.

commit message

It should direct to prefix every commit made for an assigned issue with its id in prefixing the message. Example:
#1234: commit message

branch name

The branch name should follow this pattern:

copilot/task/1234-issue-title
copilot/bug/1234-issue-title
copilot/feature/1234-issue-title

The word "task", "bug" or "feature" shall be derived from the issue type.

Side note: update .github/pr-labeler.yml to account for those new branches starting with "copilot/" as defined here, adding to what is already configured there.

Side note: update the regex in .husky/post-checkout to find the issue branches from copilot as well, on top of what it now finds in non-copilot branches (which follow the same pattern only without the leading "copilot/")

pr title

The pull request title should be similar to the branch name. Example:

Branch: copilot/task/1234-issue-title
Pr title: task/1234 issue title

Pr description

This text should follow the structure of .github/PULL_REQUEST_TEMPLATE.md

relationship

The PR shall be made related to the issue it was created for

labels

The repo has many "components" labels based on the class names in lib/metadataTypes. These labels are always prefixes with "c/". Example: "c/journey".
Based on changed classes in that above folder, try to assign pre existing labels to the pr.

milestone

assign the same milestone to the pr that the issue has assigned. </issue_description>

Comments on the Issue (you are @copilot in this section)


📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

…kout for copilot branches

Co-authored-by: JoernBerkefeld <1917227+JoernBerkefeld@users.noreply.github.com>
Copilot AI changed the title [WIP] [TASK] Create copilot-instructions.md file in .github directory task: create copilot-instructions.md and update branch/hook support for copilot agents Mar 15, 2026
Copilot AI requested a review from JoernBerkefeld March 15, 2026 09:26
@JoernBerkefeld JoernBerkefeld marked this pull request as ready for review March 15, 2026 09:38
@github-actions
Copy link

github-actions bot commented Mar 15, 2026

Coverage Report

Commit:b30b53d
Base: develop@30e9e94

Type Base This PR
Total Statements Coverage  71.07%  71.07%  (+0%)
Total Branches Coverage  70.76%  70.78%  (+0.02%)
Total Functions Coverage  83.77%  83.77%  (+0%)
Total Lines Coverage  71.07%  71.07%  (+0%)
Details (changed files):
File Statements Branches Functions Lines

@JoernBerkefeld JoernBerkefeld linked an issue Mar 15, 2026 that may be closed by this pull request
@JoernBerkefeld JoernBerkefeld added this to the 9.0.3 - dataExtensions milestone Mar 15, 2026
@JoernBerkefeld JoernBerkefeld merged commit d6bf05e into develop Mar 15, 2026
10 checks passed
@JoernBerkefeld JoernBerkefeld deleted the copilot/copilottask1234-create-copilot-instructions-md branch March 15, 2026 09:54
@JoernBerkefeld JoernBerkefeld changed the title task: create copilot-instructions.md and update branch/hook support for copilot agents task/2549 create copilot-instructions.md and update branch/hook support for copilot agents Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[TASK] create copilot-instructions.md

2 participants