Skip to content
This repository has been archived by the owner on Dec 5, 2019. It is now read-only.

Wildcards in branch name for testing feature branches #122

Open
ianheggie opened this issue Nov 8, 2013 · 3 comments
Open

Wildcards in branch name for testing feature branches #122

ianheggie opened this issue Nov 8, 2013 · 3 comments

Comments

@ianheggie
Copy link
Contributor

It would be great if we could put a wildcard in branches, eg t[0-9]* which would match our feature branches (we name the branches tNNN_some_description_here where NN is the trac ticket number

This would match possibly multiple branches, with the latest version in each branch being tested.

What do people think?

@seanmarcia
Copy link
Contributor

This doesn't seem like a bad idea even though I'm not sure I'd get much use out of it. I think I'd probably revert to manually entering the branch name to ensure it is testing the correct one and not an incorrectly labelled version.

@ianheggie
Copy link
Contributor Author

I use a lot of feature branches labeled tNNN_some_description (where NNN is the ticket number) ... having them automatically tested would be great.

@seanmarcia
Copy link
Contributor

crickets

I've never used that convention. My branches tend to be things like "integrated_cas" and then something like "integrate_cas_with_tdd" which I suppose it something like yours but would require a lot of additional customization.

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

2 participants