Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakarta.ee-spec.committee] Changes for TCK certification request

Ah, yes, much nicer!  But I guess we need someone with admin privileges on the GitHub repos to enable all of that?

And I'd like to see feedback from other on the template...

Scott Stark wrote on 7/24/19 4:01 PM:
The instructions for creating the issue templates is here:

You would have to do this in a fork where you have admin access and then merge the resulting 
File into the upstream repo. 

When you go into the admin interface for templates, they have standard templates for bug and feature requests that you could enable so that all three requests are equal. I did this for our injection-api fork, so if you go there now and choose new:

You see:


I have moved the template for the spec committee repo to here with the two suggested changes:
https://github.com/jakartaee/specification-committee/pull/3


On Jul 24, 2019, at 3:01 PM, Bill Shannon <bill.shannon@xxxxxxxxxx> wrote:

Scott Stark wrote on 7/24/19 2:06 PM:
If you go to this fork of the injection-api project and start a new issue:
https://github.com/jakartaredhat/injection-api/issues/new/choose

You will see the ‘’ issue type, and clicking that shows the template content.
Can you document how to add that template to a TCK repo such that someone submitting an issue gets to choose between a "regular" issue and a certification request?  The way it looks in the link above, it appears that a certification request is the primary issue type, with a regular issue is almost buried.  That seems wrong.  Maybe a template for "regular" issues needs to be created as well?

A PR to add a template file to the spec committee repo is:
Shouldn't this be in the specification-committee repo?  It's more content related to specification committee operations than it is content for the web site listing all the specifications.





Back to the top