You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Fix release markdown rendering of double newlines #176
Because there's a double newline between two lists, markdown renders every item with double newlines and considers the two lists as one.
The workaround is to put some non-list element between the lists.
Current behavior
markdown source
### Release Notes for [0.19.1](https://github.com/perftools/xhgui/milestone/19)
0.19.x bugfix release (patch)
### 0.19.1
- Total issues resolved: **0**
- Total pull requests resolved: **4**
- Total contributors: **2**
- [442: Cleanup: Remove adding ext-phar for build in Dockerfile](https://github.com/perftools/xhgui/pull/442) thanks to @glensc
- [441: Set GIT_AUTHOR_NAME/GIT_AUTHOR_EMAIL via env rather secrets](https://github.com/perftools/xhgui/pull/441) thanks to @glensc
- [438: Feature: Add driver name to PdoRepository](https://github.com/perftools/xhgui/pull/438) thanks to @glensc
- [436: Implement pdo: getForUrl(), getPercentileForUrl(), getAll()](https://github.com/perftools/xhgui/pull/436) thanks to @fengqi
Expected behavior
markdown source
### Release Notes for [0.19.1](https://github.com/perftools/xhgui/milestone/19)
0.19.x bugfix release (patch)
### 0.19.1
Summary:
- Total issues resolved: **0**
- Total pull requests resolved: **4**
- Total contributors: **2**
Pull requests:
- [442: Cleanup: Remove adding ext-phar for build in Dockerfile](https://github.com/perftools/xhgui/pull/442) thanks to @glensc
- [441: Set GIT_AUTHOR_NAME/GIT_AUTHOR_EMAIL via env rather secrets](https://github.com/perftools/xhgui/pull/441) thanks to @glensc
- [438: Feature: Add driver name to PdoRepository](https://github.com/perftools/xhgui/pull/438) thanks to @glensc
- [436: Implement pdo: getForUrl(), getPercentileForUrl(), getAll()](https://github.com/perftools/xhgui/pull/436) thanks to @fengqi
Potentially feasible, but this application was never designed for customization, rather quick iteration and ease of use (which is quite a challenge already, given the GPG requirements).
IMO forking + customizing is the way to go here, as it is not a library, but an application.
If I can get rid of a config setting, and instead make it a default, I'll gladly do that instead.
Yes, and that's no big deal, especially if you just need one of the many commands.
It is intentional/by design.
EDIT: in fact, give it a shot - if all you need is a single command to override, writing your own little script that uses symbols from this library should be enough, and quicker to write/easier to maintain than actually inventing a configuration DSL.
The only thing non-grouped will do is set that label to anything without a group. Will improve the wording, also not sure if non-grouped is the right term here 🤐
Activity
glensc commentedon Jan 18, 2022
If you don't want to make changes to markdown formatting, is there a way to customize this in project I use?
Ocramius commentedon Jan 18, 2022
IIRC, the markdown is generated by https://github.com/jwage/changelog-generator
To customize the release text, you would implement
CreateReleaseTextyourself:automatic-releases/src/Github/CreateReleaseText.php
Lines 13 to 34 in 41da249
Then inject it in the command:
automatic-releases/src/Application/Command/ReleaseCommand.php
Lines 37 to 61 in 41da249
This is probably best done by having your own
bin/consolereplacement:automatic-releases/bin/console.php
Lines 53 to 172 in 41da249
Note how
bin/consoleis really just doing some DI setup :)glensc commentedon Jan 18, 2022
I was hoping of configuration via:
not forking code and ecosystem around it 🗡️
but, have you though of having a container to define dependencies, like:
so, I could provide my override container if just want to wiggle few bits.
Ocramius commentedon Jan 18, 2022
Potentially feasible, but this application was never designed for customization, rather quick iteration and ease of use (which is quite a challenge already, given the GPG requirements).
IMO forking + customizing is the way to go here, as it is not a library, but an application.
If I can get rid of a config setting, and instead make it a default, I'll gladly do that instead.
Ocramius commentedon Jan 18, 2022
Very similar/related: Roave/BackwardCompatibilityCheck#377
In fact,
bin/consoleis the only thing to replace.glensc commentedon Jan 18, 2022
but that's replacing whole bin/console content... instead of just overriding single thing: $container->set(SOMEDEPENDENCY, SOMETHINGELSE)
Ocramius commentedon Jan 18, 2022
Yes, and that's no big deal, especially if you just need one of the many commands.
It is intentional/by design.
EDIT: in fact, give it a shot - if all you need is a single command to override, writing your own little script that uses symbols from this library should be enough, and quicker to write/easier to maintain than actually inventing a configuration DSL.
WyriHaximus commentedon Jan 23, 2022
@Ocramius Will this do? jwage/changelog-generator#71
Ocramius commentedon Jan 23, 2022
Most likely, ya - not sure about the difference in output between grouped/non-grouped: the tests are quite hard to read
WyriHaximus commentedon Jan 23, 2022
The only thing non-grouped will do is set that label to anything without a group. Will improve the wording, also not sure if non-grouped is the right term here 🤐