Newsletter 357 german #2358
Newsletter 357 german #2358
Conversation
| @@ -171,4 +171,4 @@ für weitere Informationen zu Payjoin v2. | |||
| [multiprocess project]: https://github.com/ryanofsky/bitcoin/blob/pr/ipc/doc/design/multiprocess.md | |||
| [news320 ipc]: /en/newsletters/2024/09/13/#bitcoin-core-30509 | |||
| [news264 payjoin]: /en/newsletters/2023/08/16/#serverless-payjoin | |||
| [news353 pr review]: /de/newsletters/2025/05/09/#bitcoin-core-pr-review-club | |||
There was a problem hiding this comment.
This should have worked, what problem did you see?
There was a problem hiding this comment.
As discussed out of band, the source of the issue was identified as this feature branch having branched off from master before the German newsletter 353 had been merged which is why the link 404'd in the preview.
There was a problem hiding this comment.
Sorry, the build process failed because you are linking to a missing file. Our build pipeline is much more observant than I expected. 😁
I think the easiest fix would then be to merge upstream/master into this pull request.
Please let me know when you think this is ready for merge by changing the pull request from Draft to Ready for Review.
Walpurga03
force-pushed
the
newsletter-357-german
branch
from
150cd4d to
d9bcb1a
Compare
|
Irgendwie ist in diesem Force-push die Änderung von "Sicherheitserwägungen" zu "Sicherheitsabwägungen" zurückgenommen worden und es wird wieder auf den englischen Newsletter verlinkt. Was ich vorschlagen wollte ist: Danach sollte der Link zum deutschen Newsletter funktionieren (da der Newsletter jetzt im gleichen Branch existiert). Die Änderung zu "Sicherheitsabwägungen" würde ich auch wieder einfügen. Wenn wir dann dieses Pull Request in den @Walpurga03: Magst du das machen oder soll ich es machen? |
No description provided.