+[2020-06-01T01:15:49Z]heywoodi can probably figure out everything from the command line, i guess. +[2020-06-01T02:11:56Z]twbDoes github understand license declarations in DEP-5 format (https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/) ? +[2020-06-01T04:38:23Z]twbApparently not: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/licensing-a-repository#detecting-a-license +[2020-06-01T04:42:20Z]twbWhich leads to https://github.com/licensee/licensee/issues/333 +[2020-06-01T20:31:43Z]mattflyin a github app what permissions do i need to allow my application modifying and creating gists?
Which leads to https://github.com/licensee/licensee/issues/333
+[2020-06-02T10:01:38Z]jennishello, I'm having a bad time googling the right thing here... I have two jobs in a workflow that execute very similar initial steps. I wondered whether it was possible to put these in some kind of template (I know that's how it's referred to in GitLab) and then call in the template at the start of the job? +[2020-06-02T15:12:15Z]mydog2morn peeps +[2020-06-02T16:24:42Z]nedbatmydog2: btw, not sure if you are waiting for a greeting. on irc, it works better to just jump right in with the topic +[2020-06-02T17:25:05Z]peepsalotis there any possibly solution for uploading CI artifacts to a project's own web server? we currently have a solution that can upload test results, but it only functions for PRs created from the main repo. PRs from forks of the project can't get permission unless we share secret keys with said forks? +[2020-06-02T17:54:33Z]Puff420hello