gojimmypi/pages:migration into main Update some github to codeberg links.
Not included are: some release links, badges, CI, bad links (see #65), and discussion / wiki (see blackmagic-debug/blackmagic#2202)
@ -289,48 +289,48 @@ For more details please refer to the ChangeLog down below.
We have had 43 individuals contribute 1265 commits since the v1.9.2 release.
Contributor (Contributions)
dragonmux (896)
the spaces at the end of these lines are unfortunately necessary. If they are missing the resulting text breaks. You can't auto remove trailing spaces in markdown unfortunately as it causes problems.
May I interest you in using markdown - for list items now, instead of the trailing spaces?
yeah fair enough, I think it was not as compact as just a pure list of items. But yeah, this works.
7576044cab
to 755438b632
There are a small handful of things that need tweaking before we can merge this - mostly GitHub still being in link text for links now going to Codeberg. Once those are addressed though we'll be happy to merge this - thank you for going through sorting this!
@ -5,3 +5,3 @@
* Join the [Discord channel](https://discord.gg/P7FYThy)
* Join the [mailing list](http://sourceforge.net/p/blackmagicdebug/mailman/)
* Edit this [website on GitHub](https://github.com/blackmagic-debug/black-magic-org)
* Edit this [website on GitHub](https://codeberg.org/blackmagic-debug/black-magic-org)
The link text should be updated here too to read website on Codeberg, and this repo (pages) replaces black-magic-org in the URI itself.
@ -12,3 +12,3 @@
## Getting the project source
The project resides in a [GitHub git repository](https://github.com/blackmagic-debug/blackmagic)
The project resides in a [GitHub git repository](https://codeberg.org/blackmagic-debug/blackmagic)
Same comment about GitHub in the link text
@ -121,3 +121,3 @@
## ST-Link v2
Instructions to restore an ST-Link v2 with recent original ST firmware can be found on [GitHub in the stlink platform README](https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms/stlink#reverting-to-original-st-firmware-with-running-bmp-firmware).
Instructions to restore an ST-Link v2 with recent original ST firmware can be found on [GitHub in the stlink platform README](https://codeberg.org/blackmagic-debug/blackmagic/src/main/src/platforms/stlink#reverting-to-original-st-firmware-with-running-bmp-firmware).
GitHub in the link text
@ -127,3 +127,3 @@
## Why is XXX not supported?
Because nobody implemented the required functions yet. Look on [GitHub](https://github.com/blackmagic-debug/blackmagic/pulls) if there is a pending pull request for your target. Consider testing PRs that try to implement the desired target to help us triage merge of new hardware support.
Because nobody implemented the required functions yet. Look on [GitHub](https://codeberg.org/blackmagic-debug/blackmagic/pulls) if there is a pending pull request for your target. Consider testing PRs that try to implement the desired target to help us triage merge of new hardware support.
GitHub in the link text
@ -107,3 +107,3 @@
* You can find the newest pre-built binaries on the
[GitHub Release Page](https://github.com/blackmagic-debug/blackmagic/releases).
[GitHub Release Page](https://codeberg.org/blackmagic-debug/blackmagic/releases).
GitHub in the link text
@ -147,3 +147,3 @@
To upgrade non-native hardware see the READMEs of the different
[platforms on GitHub](https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms).
[platforms on GitHub](https://codeberg.org/blackmagic-debug/blackmagic/src/main/src/platforms).
Ditto
@ -168,3 +168,3 @@
To upgrade non-native hardware see the readme of the different
[platforms on GitHub](https://github.com/blackmagic-debug/blackmagic/tree/main/src/platforms).
[platforms on GitHub](https://codeberg.org/blackmagic-debug/blackmagic/src/main/src/platforms).
And again
@ -9,3 +9,3 @@
## Getting the project source
The project resides in a [GitHub git repository](https://github.com/blackmagic-debug/blackmagic)
The project resides in a [GitHub git repository](https://codeberg.org/blackmagic-debug/blackmagic)
GitHub in the link text
We'll use our review notes from here, given Esden already merged this, as a template of what additional cleanup is needed in a follow-up PR (what to check for in his fix/codeberg branch). There is no action needed from you, Jimmy - we just didn't see that the PR had already been reviewed and merged when we finished writing this set of notes.
Sorry @dragonmux I guess I am bit too tired and let it all slip through. Should we just merge my fixes, considering it is not being automatically deployed yet anyways? Then Jimmy or you could clean up the remaining strings?
My bad: I completely skipped the text, as I was only looking at links. I'm happy to submit additional PR.
It's all good - no harm done given the lack of auto-deployments.. if you want to turn your branch into a PR we can certainly give it a look over and see about getting it merged to clear the way for some further fixups, especially as Jimmy's offering.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?