Post issues to inactive tracks

[kytrinyx]

If a track that has not yet been activated has implemented an exercise then the issue is relevant.

If the issue is not specific to an exercise (such as documentation across the board), then it is also relevant to inactive tracks; perhaps even more so, since tracks often languish in an unstarted/inactive state for a long time before someone decides to port enough exercises to make it live, and the starter repository will have lots of old references in it.

@petertseng What do you think?

[petertseng]

Seems like good reasoning, and dry runs of ./blazon -body B -title T and ./blazon -body B -title T -exercise hello-world both seem to give good lists, so I'm OK with this.

If it is required in the future, perhaps flags to indicate active-only or inactive-only would be useful, but they can be left for a time when we know we need them. I don't currently see a need for the flags.

[kytrinyx]

Yeah, I actually implemented those flags and then threw it away, because I didn't see the need for them. I think this default is reasonable.

[kytrinyx]

(note: PR is failing because I had forgotten to turn on the "only run travis build if there's a travis.yml file")

[petertseng]

Great, that settles it for me then. :+1:

Another potential idea is to print out something like:

This issue would be submitted to the following tracks:
- ceylon (inactive)
- ruby

[kytrinyx]

Ah, I like that. It's not critical, but it's a very nice touch.

[kytrinyx]

OK, I've updated the output:

$ blazon -title="The Title" -body="Do work." -exercise=sublist
Title:
The Title

Body:
Do work.

This issue would be submitted to the following tracks:
- elixir
- elm (inactive)
- haskell
- lua
- perl5
- python
- rust
- scala

To submit, rerun the command with the -yes flag.

[petertseng]

I say :+1:

[kytrinyx]

Thanks for reviewing!