Skip to content
This repository has been archived by the owner on Jan 17, 2024. It is now read-only.

Pull Request Status Menu for policy regardless of genre #142

Open
pinkfloydx33 opened this issue Dec 3, 2019 · 0 comments
Open

Pull Request Status Menu for policy regardless of genre #142

pinkfloydx33 opened this issue Dec 3, 2019 · 0 comments

Comments

@pinkfloydx33
Copy link

Is it possible to create a pull request status menu for any genre so long as the statusName matches? Think of a custom policy that is similar to Azure DevOps' built in code coverage check. The name of that status is "codecoverage" but the genre is the lowercase name of the build definition it's running against. This means you end up with multiple genres within the same policy-name--one for each build.

We have a custom policy that does something similar and would like to create a pull request status menu. The problem is, it seems that both statusName and statusGenre are required while what I need is to match my policy's name regardless of the genre. I've tried omitting statusGenre, setting it to null, "" and even tried "*" to no avail. Of course if I set the genre to the name of one of my builds I get a menu, but I don't want to have to do this for each build.

Is there some syntax that makes this possible or am I out of luck?

"contributions": [
	{
		"id": "my-pr-status-menu",
		"type": "ms.vss-web.menu",
		"description": "Status menu for status with name 'my-pr-policy'",
		"targets": [
			"ms.vss-code-web.pull-request-status-menu"
		],
		"properties": {
			"statusGenre": "WHAT TO PUT HERE?",
			"statusName": "my-pr-policy"
		}
	},
	{
		"id": "my-pr-status-menu-item-requeue",
		"type": "ms.vss-web.action",
		"description": "Requeues the Pull Request Policy",
		"targets": [
			".my-pr-status-menu"
		],
		"properties": {
			"text": "Requeue Policy",
			"title": "ms.vss-code-web.pull-request-status-menu",
			"icon": "css://bowtie-icon bowtie-status-run-outline",
			"group": "actions",
			"uri": "main.html",
			"registeredObjectId": "myPrPolicyRequeue"
		}
	}
]
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant