Closed pixlwave closed 3 months ago
Warnings | |
---|---|
:warning: | Some of the commits are missing ticket numbers. Please consider squashing all commits that don't have a tracking number. |
Generated by :no_entry_sign: Danger Swift against 3c6540e69e0e031793212f9fdd606a21d408bb36
Oh yeah, Stefan asked this. Let's try in the test repo.
LGTM but what happens if a pr has multiple labels? Would it appear under multiple categories?
This PR had 3 tags, and the first one (I assume from the release.yml ordering) got chosen.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 78.05%. Comparing base (
567f22b
) to head (c82691d
).:exclamation: Current head c82691d differs from pull request most recent head 3c6540e
Please upload reports for the commit 3c6540e to get more accurate results.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Issues
0 New issues
0 Accepted issues
Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code
We weren't using Towncrier very well so this PR replaces it with the use of GitHub's generated release notes along with a configuration that will categorise each entry based upon one of the following labels being applied:
Labels added here: https://github.com/element-hq/element-x-ios/labels?q=pr-
These labels can be added after the PR is merged, so long as they're there before the release is made.
The second commit removes Towncrier. I made a second repo to figure the flow out, but not sure how to validate the changes on EX other than wait for the next release and tidy up anything that comes out of that.