[CLEANUP] adding & utilising composer sort-packages

[SignpostMarv]

No description provided.

[oliverklee]

@SignpostMarv A request for future commit message (I'll update this PR's message on merging):

After the code for the type of change ([FEATURE], [BUGFIX], [CLEANUP] or [TASK]), please start the commit subject as a continuation of "This commit will …", e.g, "Add …" or "Fix …". Thanks!

[oliverklee]

Looks good, thanks!

[SignpostMarv]

After the code for the type of change ([FEATURE], [BUGFIX], [CLEANUP] or [TASK]), please start the commit subject as a continuation of "This commit will …", e.g, "Add …" or "Fix …". Thanks!

• [CLEANUP] add package sorting option to composer config
• [CLEANUP] this commit re-requires a package to enact composer sort-packages

or

• [CLEANUP] add package sorting option to composer config
• this commit re-requires a package to enact composer sort-packages

?

[oliverklee]

@SignpostMarv I don't quite understand your question. Maybe an example for a (fictional) single commit message will help:

(Subject) [BUGFIX] Warn if the HTML is empty

(Description) Previously, inlining CSS for empty HTML was possible, although this indicates that the inliner was called with broken data. Now the CssInliner will throw an exception, making it easier to solve the root cause of the empty HTML.

[oliverklee]

@SignpostMarv For more details, I can recommend this blog post: https://chris.beams.io/posts/git-commit/

[SignpostMarv]

Maybe an example for a (fictional) single commit message will help:

ah; I very rarely use extended commit messages. there's a butt load of commits coming on the rebased #778 branch:

will rebase these once I'm done to reword them appropriately before force-pushing.

[oliverklee]

One-liners are perfectly fine as long as there is nothing useful to add in addition to the commit message subject/heading.

[SignpostMarv]

One-liners are perfectly fine as long as there is nothing useful to add in addition to the commit message subject/heading.

mutli-liners when resolving psalm issues may prove useful to those unfamiliar with psalm typehinting syntax.

[JakeQZ]

ah; I very rarely use extended commit messages. there's a butt load of commits coming on the rebased #778 branch:

The title of the initial commit is potentially most important. When squashing-and-merging, we can edit the commit message, but it will typically begin with that from the first commit.

If you encounter any issues rebasing, you might like to reference my post at #373 (comment) for guidance, and possibly @oliverklee's at #708 (comment) if anything goes awry. Thanks again for contributing 🥰