{"push_id":2617859349,"size":3,"distinct_size":1,"ref":"refs/heads/marc/issues/83-build-improvements","head":"84c4421b7239a0305b344979df41831065783df0","before":"5e12ac343befdbcc0e5f366a36d7ab73ec6899b3","commits":[{"sha":"efaf553d1d08537b1a0bf789298aa939444e4026","author":{"name":"Marc Philipp","email":"d33c80bc45d65303e33ca83108a9952b745af9ef@gradle.com"},"message":" Introduce TempDirectory Jupiter Extension (#39 / #69)\n\nThe `TempDirectory` extension can be used to create and clean up a\r\ntemporary directory for an individual test or all tests in a test class.\r\nTo use it, simply register the extension and add a parameter of type\r\n`java.nio.file.Path` to your test or lifecycle method or constructor:\r\n\r\n  @ExtendWith(TempDirectory.class)\r\n  class Tests {\r\n    @Test\r\n    void test(@TempDir Path tempDir) throws Exception {\r\n      Path file = tempDir.resolve(\"test.txt\");\r\n      writeFile(file);\r\n      assertExpectedFileContent(file);\r\n    }\r\n  }\r\n\r\nIn addition to the default file system, the extension can be used with\r\nany FileSystem implementation, e.g. Jimfs [1]. In order to use a custom\r\nfile system, simply register the extension programmatically and pass a\r\nprovider of a custom parent directory of type `Path` to the static factory\r\nmethod `TempDirectory::createInCustomDirectory`\r\n\r\n[1] https://github.com/google/jimfs","distinct":false,"url":"https://api.github.com/repos/junit-pioneer/junit-pioneer/commits/efaf553d1d08537b1a0bf789298aa939444e4026"},{"sha":"15cb92c76f48d42ddad9cc18c2dfa480982d5b27","author":{"name":"Nicolai Parlog","email":"04dd9b991c76bb3c7355e3b95f2a0c987d211d87@codefx.org"},"message":"Move issue and PR numbers to message body\n\nThe contribution guidelines defined the following outline for commit\r\nmessages, where the first line (let's call it \"title\") has an ideal\r\nlength of 50 characters, with a maximum of 70:\r\n\r\n${action} (${issues} / ${pull-request})\r\n\r\n${body}\r\n\r\nMentioning issue and pull request numbers in the title has the\r\nadvantage of making them very visible, for example in\r\n`git log --oneline` and GitHub's UI, but has the downside of severely\r\nreducing the number of available characters for the title itself.\r\nOnce we cross into three digit issue/PR numbers `(#abc / #xyz)` eats\r\nup at least 14 characters - that's not good.\r\n\r\nThe new guideline places issue and pull request number at the bottom\r\nof the message:\r\n\r\n```\r\n${action}\r\n\r\n${body}\r\n\r\n${references}: ${issues}\r\nPR: ${pull-request}\r\n```\r\n\r\nHere, `${references}` is usually _Closes_, _Fixes_, or _Resolves_,\r\nbut if none of that is the case, can also be _Issue(s)_.\r\n\r\nCloses: #79\r\nPR: #86","distinct":false,"url":"https://api.github.com/repos/junit-pioneer/junit-pioneer/commits/15cb92c76f48d42ddad9cc18c2dfa480982d5b27"},{"sha":"84c4421b7239a0305b344979df41831065783df0","author":{"name":"Marc Philipp","email":"1d6e1cf70ec6f9ab28d3ea4b27a49a77654d370e@marcphilipp.de"},"message":"Simplify Gradle publishing configuration\n\n - Let Gradle set up task dependencies for sourcesJar and javadocJar\n   automatically\n - Upgrade to Gradle 4.8 to use built-in support for signing\n   publications and configuring the POM\n - Use single publishing repo and remove custom configuration that\n   ensured that only snapshots were published to the snapshot repo and\n   releases to the staging repo\n\nResolves: #83","distinct":true,"url":"https://api.github.com/repos/junit-pioneer/junit-pioneer/commits/84c4421b7239a0305b344979df41831065783df0"}]}
{"actor":{"display_login":"marcphilipp"}}