That could work. In a similar way to how we have the compilation tasks. Michał.
On 4 Jun 2017, 13:57 +0200, José Valim <[email protected]>, wrote: > > If we really want to push it, GitHub new issue link allows passing title & > >body query options to fill the template. > > Actually, automatically opening up a page with data filled is one of the > reasons I prefer individual tasks. We can also have a `mix report` task that > asks: > > Do you want to open up an issue for? > > 1. elixir > 2. ecto > 3. phoenix > > And the list is based on the available report.* tasks. > > > > José Valim > www.plataformatec.com.br > Skype: jv.ptec > Founder and Director of R&D > > > On Sun, Jun 4, 2017 at 1:42 PM, Michał Muskała <[email protected]> wrote: > > > On 4 Jun 2017, 13:39 +0200, José Valim <[email protected]>, > > > wrote: > > > > > > > I think this is a great idea. > > > > > > > > Question: if someone is using Ecto and Phoenix, and they need to open > > > > up a bug in Ecto, how can they do so without all of the Phoenix > > > > metadata? > > > > > > > > That said, wouldn't it be better for each of those projects to > > > > introduce report.ecto / report.phoenix individually? Then they have > > > > full control on the report. If by any chance we see some duplication, > > > > then we can introduce helper functions. That would be more flexible > > > > than wrapping the whole functionality. > > > > > > > > > > I was thinking about this and I'm not sure this is better. There might be > > > some additional information, but if everything is properly sectioned, I > > > don't think it's going to be a huge issue. It will also "just work" for > > > projects that don't need to add additional information. Another thing to > > > consider is that often, an issue created in phoenix is actually something > > > wrong with ecto, so having all this information already there would be > > > helpful. > > > > > > Having one task creates an excellent workflow - do you have any issues > > > with something elixir-related? Run `mix report` and open an issue. That's > > > it. With separate tasks, you need to figure out the appropriate task to > > > run - first find out if it's even there. > > > > > > If we really want to push it, GitHub new issue link allows passing title > > > & body query options to fill the template. I could imagine running `mix > > > report phoenix` which would open an issue on the phoenix repo with filled > > > template (provided project has the GitHub link). That might be going a > > > bit too far, though. > > > -- > > > You received this message because you are subscribed to the Google Groups > > > "elixir-lang-core" group. > > > To unsubscribe from this group and stop receiving emails from it, send an > > > email to [email protected]. > > > To view this discussion on the web visit > > > https://groups.google.com/d/msgid/elixir-lang-core/4564c0ed-a1eb-4ccd-bc40-9fb018a9b4ab%40Spark. > > > > > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4J%3DRF7BHCYVdejQaVSragrNkrq%3DQnv9-49JvHV_UOqbig%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/53cd9196-798f-4467-a34a-7f9c20e9037f%40Spark. For more options, visit https://groups.google.com/d/optout.
