#towncrier — Public Fediverse posts

Youth Hockey: Wildcats beat Rockets, advance to finals | Sports https://www.rawchili.com/nhl/540634/ #BraydenWarford #BrendanCyr #Centre(iceHockey) #EvanJageler #goaltender #GraysonLynch #HaverhillValleyForum’sBlueRink #Hockey #IceHockey #JaydnOnos #JohnnyRaposo #MasonKing #MathewDesmond #MatthewFogg #MatthewRiley #NorthCentralMassSting­ers #reading #ReadingRockets #Saugus #SeasonsInAmericanIceHockey #Stel­laHardiman #TownCrier #Wilming­tonWildcatsBantam1Squad #Wilmington #ZachStroud

Been playing around with #towncrier for the past couple of days.
I like its approach to creating & updating changelogs(plus its support for both .md & .rst output)

Between its clear tutorial and referencing pipx & pytest's usage of the package, I think it's going to be an easy add-on to my projects. Plus, I really need to get better disciplined at writing regular consistent #Changelog

https://towncrier.readthedocs.io/en/stable/tutorial.html

#Python

Been playing around with #towncrier for the past couple of days.
I like its approach to creating & updating changelogs(plus its support for both .md & .rst output)

Between its clear tutorial and referencing pipx & pytest's usage of the package, I think it's going to be an easy add-on to my projects. Plus, I really need to get better disciplined at writing regular consistent #Changelog

https://towncrier.readthedocs.io/en/stable/tutorial.html

#Python

Been playing around with #towncrier for the past couple of days.
I like its approach to creating & updating changelogs(plus its support for both .md & .rst output)

Between its clear tutorial and referencing pipx & pytest's usage of the package, I think it's going to be an easy add-on to my projects. Plus, I really need to get better disciplined at writing regular consistent #Changelog

https://towncrier.readthedocs.io/en/stable/tutorial.html

#Python

Been playing around with #towncrier for the past couple of days.
I like its approach to creating & updating changelogs(plus its support for both .md & .rst output)

Between its clear tutorial and referencing pipx & pytest's usage of the package, I think it's going to be an easy add-on to my projects. Plus, I really need to get better disciplined at writing regular consistent #Changelog

https://towncrier.readthedocs.io/en/stable/tutorial.html

#Python

Been playing around with #towncrier for the past couple of days.
I like its approach to creating & updating changelogs(plus its support for both .md & .rst output)

Between its clear tutorial and referencing pipx & pytest's usage of the package, I think it's going to be an easy add-on to my projects. Plus, I really need to get better disciplined at writing regular consistent #Changelog

https://towncrier.readthedocs.io/en/stable/tutorial.html

#Python

It’s time to go Garden-ing, again: Tewksbury High boys hockey beats Westwood, plays for state title Sunday | Sports https://www.allforgardening.com/1656487/its-time-to-go-garden-ing-again-tewksbury-high-boys-hockey-beats-westwood-plays-for-state-title-sunday-sports/ #AaronSosa #ChelmsfordForum #ColeAbruzi #ConnorBlaney #garden #JacksonFeudo #KevinAndriolo #LukeMartin #MattyDonovan #MiaaDivision2BoysHockeyTournament #MichaelMacauda #SeanJoyce #SebO’brien #semifinals #TdGarden #tewksbury #TewksburyCoachDerekDoherty #TownCrier #TylerBourgea #westwood

It’s time to go Garden-ing, again: Tewksbury High boys hockey beats Westwood, plays for state title Sunday | Sports https://www.allforgardening.com/1656487/its-time-to-go-garden-ing-again-tewksbury-high-boys-hockey-beats-westwood-plays-for-state-title-sunday-sports/ #AaronSosa #ChelmsfordForum #ColeAbruzi #ConnorBlaney #garden #JacksonFeudo #KevinAndriolo #LukeMartin #MattyDonovan #MiaaDivision2BoysHockeyTournament #MichaelMacauda #SeanJoyce #SebO’brien #semifinals #TdGarden #tewksbury #TewksburyCoachDerekDoherty #TownCrier #TylerBourgea #westwood

Sixth graders get into Ancient Egypt | News https://www.byteseu.com/1818928/ #“havingFunWithPyramidsAndPharaohs” #AncientEgypt #AncientEgyptianReligion #culture #Egypt #EgyptologistPauletteMo­rin #Egyptology #EyeOfHo­rus #Heart #jewellery #JohnFRyanSchool #KristinRomano #LotusFlower #mum­mification #MuseumOfFineArts #ParentAdvisoryCouncil(pac) #SixthGradeStudents #Tewksbury #TownCrier

https://www.europesays.com/africa/97344/ Sixth graders get into Ancient Egypt | News #“havingFunWithPyramidsAndPharaohs” #AncientEgypt #AncientEgyptianReligion #culture #Egypt #EgyptologistPauletteMo­rin #egyptology #EyeOfHo­rus #Heart #jewellery #JohnFRyanSchool #KristinRomano #LotusFlower #mum­mification #MuseumOfFineArts #ParentAdvisoryCouncil(pac) #SixthGradeStudents #tewksbury #TownCrier

Youth hockey: Wildcats fly past Sachems | Sports https://www.rawchili.com/nhl/388671/ #Bantam2Players #BraydenDoe #BrendanCyr #BrianDoherty #CodyMacdonald #EvanJageler #goaltender #Hockey #IceHockey #JackFennelly #JohnnyRaposo #JoshSai­ja #MaldenValleyFor­um #MasonDesmond #sports #TownCrier #Wilmington #WilmingtonBantam1Squad #Winches­terYouthHockeySa­chems #ZachStroud

Finally released a new version 0.5.0a0 of `sphinxcontrib-towncrier` — my #Sphinx extension for injecting future draft/unreleased bits of Towncrier-managed change logs.

The main theme of this version is supporting Towncrier 24.7.0rc1 and higher.

#Python #Towncrier

Finally released a new version 0.5.0a0 of `sphinxcontrib-towncrier` — my #Sphinx extension for injecting future draft/unreleased bits of Towncrier-managed change logs.

The main theme of this version is supporting Towncrier 24.7.0rc1 and higher.

#Python #Towncrier

Finally released a new version 0.5.0a0 of `sphinxcontrib-towncrier` — my #Sphinx extension for injecting future draft/unreleased bits of Towncrier-managed change logs.

The main theme of this version is supporting Towncrier 24.7.0rc1 and higher.

#Python #Towncrier

Finally released a new version 0.5.0a0 of `sphinxcontrib-towncrier` — my #Sphinx extension for injecting future draft/unreleased bits of Towncrier-managed change logs.

The main theme of this version is supporting Towncrier 24.7.0rc1 and higher.

#Python #Towncrier

Finally released a new version 0.5.0a0 of `sphinxcontrib-towncrier` — my #Sphinx extension for injecting future draft/unreleased bits of Towncrier-managed change logs.

The main theme of this version is supporting Towncrier 24.7.0rc1 and higher.

#Python #Towncrier

Hoje é dia de Live de Python! \o/

Você já se perguntou como organizar e documentar as mudanças do seu código? 🤔

Hoje, conversaremos sobre changelogs, como eles ajudam a manter seu projeto organizado e como gerá-los facilmente com Towncrier!

Às 22h! 🔥

https://youtube.com/live/ATKJXpHrBfE

🔁🔁🔁

#python #towncrier #changelogs

Hoje é dia de Live de Python! \o/

Você já se perguntou como organizar e documentar as mudanças do seu código? 🤔

Hoje, conversaremos sobre changelogs, como eles ajudam a manter seu projeto organizado e como gerá-los facilmente com Towncrier!

Às 22h! 🔥

https://youtube.com/live/ATKJXpHrBfE

🔁🔁🔁

#python #towncrier #changelogs

Hoje é dia de Live de Python! \o/

Você já se perguntou como organizar e documentar as mudanças do seu código? 🤔

Hoje, conversaremos sobre changelogs, como eles ajudam a manter seu projeto organizado e como gerá-los facilmente com Towncrier!

Às 22h! 🔥

https://youtube.com/live/ATKJXpHrBfE

🔁🔁🔁

#python #towncrier #changelogs

Hoje é dia de Live de Python! \o/

Você já se perguntou como organizar e documentar as mudanças do seu código? 🤔

Hoje, conversaremos sobre changelogs, como eles ajudam a manter seu projeto organizado e como gerá-los facilmente com Towncrier!

Às 22h! 🔥

https://youtube.com/live/ATKJXpHrBfE

🔁🔁🔁

#python #towncrier #changelogs

Hoje é dia de Live de Python! \o/

Você já se perguntou como organizar e documentar as mudanças do seu código? 🤔

Hoje, conversaremos sobre changelogs, como eles ajudam a manter seu projeto organizado e como gerá-los facilmente com Towncrier!

Às 22h! 🔥

https://youtube.com/live/ATKJXpHrBfE

🔁🔁🔁

#python #towncrier #changelogs

i wrote this #python #cli #tool last year it's pretty good.

#protokolo generates a #changelog from fragment files, kind of like #towncrier, but way less intelligently (in a good way). its purpose is to circumvent the problem where many #vcs commits attempt to edit the same section in the change log file, and they #mergeConflict all the time. (or worse, a pr that is merged late adds its change log to a previous release.)

https://protokolo.readthedocs.io/en/stable/readme.html

#development #programming #git

i wrote this #python #cli #tool last year it's pretty good.

#protokolo generates a #changelog from fragment files, kind of like #towncrier, but way less intelligently (in a good way). its purpose is to circumvent the problem where many #vcs commits attempt to edit the same section in the change log file, and they #mergeConflict all the time. (or worse, a pr that is merged late adds its change log to a previous release.)

https://protokolo.readthedocs.io/en/stable/readme.html

#development #programming #git

i wrote this #python #cli #tool last year it's pretty good.

#protokolo generates a #changelog from fragment files, kind of like #towncrier, but way less intelligently (in a good way). its purpose is to circumvent the problem where many #vcs commits attempt to edit the same section in the change log file, and they #mergeConflict all the time. (or worse, a pr that is merged late adds its change log to a previous release.)

https://protokolo.readthedocs.io/en/stable/readme.html

#development #programming #git

i wrote this #python #cli #tool last year it's pretty good.

#protokolo generates a #changelog from fragment files, kind of like #towncrier, but way less intelligently (in a good way). its purpose is to circumvent the problem where many #vcs commits attempt to edit the same section in the change log file, and they #mergeConflict all the time. (or worse, a pr that is merged late adds its change log to a previous release.)

https://protokolo.readthedocs.io/en/stable/readme.html

#development #programming #git

i wrote this #python #cli #tool last year it's pretty good.

#protokolo generates a #changelog from fragment files, kind of like #towncrier, but way less intelligently (in a good way). its purpose is to circumvent the problem where many #vcs commits attempt to edit the same section in the change log file, and they #mergeConflict all the time. (or worse, a pr that is merged late adds its change log to a previous release.)

https://protokolo.readthedocs.io/en/stable/readme.html

#development #programming #git

Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request.

Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

And a tool like #TownCrier https://towncrier.readthedocs.io/ can help a lot.

@xavdid @nedbat

Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request.

Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

And a tool like #TownCrier https://towncrier.readthedocs.io/ can help a lot.

@xavdid @nedbat

Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request.

Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

And a tool like #TownCrier https://towncrier.readthedocs.io/ can help a lot.

@xavdid @nedbat

Practically, I find it very helpful to write the change log item as an update to the change log document, included *as separately written documentation*, one change among others included in the same merge request.

Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

And a tool like #TownCrier https://towncrier.readthedocs.io/ can help a lot.

@xavdid @nedbat

Practically, I find it very helpful to write the change log item for a merge request as an update to the change log document, included *as separately written documentation* in the merge request itself.

Consider it like updating the API documentation in the same merge request that changes the API. Except here, the interface is for the humans considering whether and why to update to this version.

And a tool like #TownCrier https://towncrier.readthedocs.io/ can help a lot.

@xavdid @nedbat

I hate merge conflicts in my change logs.

I'm aware of #towncrier, but it's a bit finicky and prescriptive.

Is there another general-purpose #changelog generator, or is this something I'm going to end up writing myself?

I hate merge conflicts in my change logs.

I'm aware of #towncrier, but it's a bit finicky and prescriptive.

Is there another general-purpose #changelog generator, or is this something I'm going to end up writing myself?

I hate merge conflicts in my change logs.

I'm aware of #towncrier, but it's a bit finicky and prescriptive.

Is there another general-purpose #changelog generator, or is this something I'm going to end up writing myself?

I hate merge conflicts in my change logs.

I'm aware of #towncrier, but it's a bit finicky and prescriptive.

Is there another general-purpose #changelog generator, or is this something I'm going to end up writing myself?

I hate merge conflicts in my change logs.

I'm aware of #towncrier, but it's a bit finicky and prescriptive.

Is there another general-purpose #changelog generator, or is this something I'm going to end up writing myself?

I'm looking for something like #Scompler for Mastodon.

A tool that lets you schedule posts and analyze your interactions.

So far I've found and tried #Analytodon #Buffer #Fedilab #Fediplan #Scheduler #Seenly #Towncrier #Tweepsmap.

I made a quick table with the results of my tests: https://joinfediverse.wiki/Scheduling_and_analytic_tools_for_Mastodon

Does anybody know any other tools? Preferably something that ticks all the boxes?

I'm looking for something like #Scompler for Mastodon.

A tool that lets you schedule posts and analyze your interactions.

So far I've found and tried #Analytodon #Buffer #Fedilab #Fediplan #Scheduler #Seenly #Towncrier #Tweepsmap.

I made a quick table with the results of my tests: https://joinfediverse.wiki/Scheduling_and_analytic_tools_for_Mastodon

Does anybody know any other tools? Preferably something that ticks all the boxes?

I'm looking for something like #Scompler for Mastodon.

A tool that lets you schedule posts and analyze your interactions.

So far I've found and tried #Analytodon #Buffer #Fedilab #Fediplan #Scheduler #Seenly #Towncrier #Tweepsmap.

I made a quick table with the results of my tests: https://joinfediverse.wiki/Scheduling_and_analytic_tools_for_Mastodon

Does anybody know any other tools? Preferably something that ticks all the boxes?

I'm looking for something like #Scompler for Mastodon.

A tool that lets you schedule posts and analyze your interactions.

So far I've found and tried #Analytodon #Buffer #Fedilab #Fediplan #Scheduler #Seenly #Towncrier #Tweepsmap.

I made a quick table with the results of my tests: https://joinfediverse.wiki/Scheduling_and_analytic_tools_for_Mastodon

Does anybody know any other tools? Preferably something that ticks all the boxes?

I'm looking for something like #Scompler for Mastodon.

A tool that lets you schedule posts and analyze your interactions.

So far I've found and tried #Analytodon #Buffer #Fedilab #Fediplan #Scheduler #Seenly #Towncrier #Tweepsmap.

I made a quick table with the results of my tests: https://joinfediverse.wiki/Scheduling_and_analytic_tools_for_Mastodon

Does anybody know any other tools? Preferably something that ticks all the boxes?

Agreed @webaware, it is a clear sign that the release was made with no user-facing description of the changes.

If you don't already have the user-facing description of the change ready, it's not ready to commit to version control, and certainly not ready to release.

I like #TownCrier as a way to write a summary description of each change, committed along with the code change and assembled automatically into a user-facing change log document when it's time to release.

https://towncrier.readthedocs.io/

Agreed @webaware, it is a clear sign that the release was made with no user-facing description of the changes.

If you don't already have the user-facing description of the change ready, it's not ready to commit to version control, and certainly not ready to release.

I like #TownCrier as a way to write a summary description of each change, committed along with the code change and assembled automatically into a user-facing change log document when it's time to release.

https://towncrier.readthedocs.io/

Agreed @webaware, it is a clear sign that the release was made with no user-facing description of the changes.

If you don't already have the user-facing description of the change ready, it's not ready to commit to version control, and certainly not ready to release.

I like #TownCrier as a way to write a summary description of each change, committed along with the code change and assembled automatically into a user-facing change log document when it's time to release.

https://towncrier.readthedocs.io/

Agreed @webaware, it is a clear sign that the release was made with no user-facing description of the changes.

If you don't already have the user-facing description of the change ready, it's not ready to commit to version control, and certainly not ready to release.

I like #TownCrier as a way to write a summary description of each change, committed along with the code change and assembled automatically into a user-facing change log document when it's time to release.

https://towncrier.readthedocs.io/

Agreed @webaware, it is a clear sign that the release was made with no user-facing description of the changes.

If you don't already have the user-facing description of the change ready, it's not ready to commit to version control, and certainly not ready to release.

I like #TownCrier as a way to write a summary description of each change, committed along with the code change and assembled automatically into a user-facing change log document when it's time to release.

https://towncrier.readthedocs.io/