Skip to content

[Blueprints] Accept branch names and tags in git:directory resource#2760

Merged
adamziel merged 4 commits intotrunkfrom
accept-branch-names-in-git-resource
Oct 9, 2025
Merged

[Blueprints] Accept branch names and tags in git:directory resource#2760
adamziel merged 4 commits intotrunkfrom
accept-branch-names-in-git-resource

Conversation

@adamziel
Copy link
Collaborator

@adamziel adamziel commented Oct 9, 2025

Motivation for the change, related issues

Enables sourcing data from arbitrary branches and tags via Blueprints.

Before this PR, you had to use a ref name that's either HEAD or a commit hash. With this PR, you can also reference branches by their names and tags. Also, the path property is no longer required and defaults to /.

Testing Instructions (or ideally a Blueprint)

Run this Blueprint and confirm it installs and activates the Blocky formats plugin from its Git repo:

{
  "login": true,
  "landingPage": "/wp-admin/post-new.php",
  "steps": [
    {
      "step": "installPlugin",
      "options": {
        "activate": true,
        "targetFolderName": "blocky-formats"
      },
      "pluginData": {
        "resource": "git:directory",
        "url": "https://github.com/dmsnell/blocky-formats.git",
        "ref": "trunk"
      }
    }
  ],
  "preferredVersions": {
    "php": "8.3",
    "wp": "latest"
  },
  "features": {}
}

@adamziel adamziel changed the title [Blueprints] Accept branch names in git resources [Blueprints] Accept branch names and tags in git:directory resource Oct 9, 2025
@adamziel adamziel marked this pull request as ready for review October 9, 2025 18:33
@adamziel adamziel merged commit f95e3a9 into trunk Oct 9, 2025
28 checks passed
@adamziel adamziel deleted the accept-branch-names-in-git-resource branch October 9, 2025 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant