hack bundle #17

[cordoval]

addresses #17

[dbu]

hi cordoval, what exactly is the purpose of this script? its just a git clone and checking out a branch on the clone, then adding a random file to the branch. why not simply write a shell script for this? as i understand, people would want to run that when being at a hackday, so would it not better be as standalone as possible? if i am at a hackday and want to create a branch to work on something, i don't want to install this dashboard application probably.

[pilotci]

@dbu i know is more for us that do this many times a day, at the start is simple but it will get more elaborate i thought of a lib but for now is ok, later on we can split it to a vendor third party and have the bundle decoupled

[dbu]

i am quite reluctant to add something that i don't really see how its related to the dashboard. afaikt you use nothing of the dashboard configuration or anything. actually a bash script would be enough for what you do, its executing a bunch of shell commands only. its also not putting any content into the dashboard or anything like that, or did i miss something?

[cordoval]

right it is not yet, remember it is just an idea, a stab, you don't have to merge right now, but it could lead to other things

[dbu]

okay, i will just leave the PR open for now. ping me on this if you think i should now reconsider merging it :-)

[cordoval]

some ideas i see is

• picking PRs to clone them for reproduction or QA
• pushing template description table for PRs
• relating issues or tagging them with certain tag

i also use hub for things, however sometimes ant of phing scripts for instance are not flexible enough to run programatically, we wills ee, no rush

[cordoval]

@dbu i will close this because i am merging all efforts into one PR and then also to keep things clean.