If the PR has a problem tell me to fix it.
explain enabling repository releases #597
Gnu1/Documentation:how_to_create_a_release into main Thanks, minor remarks.
@ -53,3 +53,3 @@
### On Codeberg
To create a release on Codeberg, first go to the `Releases` tab of your repository, and click on `New Release`:
To create a release on Codeberg, first go to the `Setting` of your repository, go to `Units` -> `Overview`, enable `Enable repository releases` and click on `Save setting`.
nit: Setting -> Settings
I'd say "go to your repository's Settings, click on Units -> Overview"...
@ -55,1 +55,3 @@
To create a release on Codeberg, first go to the `Releases` tab of your repository, and click on `New Release`:
To create a release on Codeberg, first go to the `Setting` of your repository, go to `Units` -> `Overview`, enable `Enable repository releases` and click on `Save setting`.
<img src="/images/collaborating/citable-code/enable_repository_releases.png" alt="enable_repository_releases">
Would be great if the alt text were descriptive ("What does this photo show? What are you emphasizing with the circles?"), as it is read out by people using a screen reader.
Admittedly, other screenshots in the docs here aren't accessible.
02d6e4ea65
b3b9b01bd7
b3b9b01bd7
c2bf1c88db
fixed
your repository's Settings,
I'm not sure that grammar of this sentence is true or false?!
But I think it is false.
c2bf1c88db
9c9328eca2
@ -55,1 +55,3 @@
To create a release on Codeberg, first go to the `Releases` tab of your repository, and click on `New Release`:
To create a release on Codeberg, first go to your repository `Settings`, click on `Units` -> `Overview`, enable `Enable repository releases` and click on `Save setting`.
<img src="/images/collaborating/citable-code/enable_repository_releases.png" alt="steps of enabling repository releases">
Hi, sorry, steps of enabling repository releases is still a bit sub-par. Can you try Screenshot of an example repository's settings with circles drawn over the buttons described in the steps above?
In this context, OK-ish alt text should describe what is shown, the text, and what you are trying to emphasize. By saying that the screenshot describes the steps above, this is better than nothing.
@n0toose wrote in #597 (comment):
@n0toose wrote in #597 (comment):
Hi, sorry,
steps of enabling repository releasesis still a bit sub-par. Can you tryScreenshot of an example repository's settings with circles drawn over the buttons described in the steps above?
No! I'm not agree. I think steps of enabling repository releases is enough, simple, small and good. But I changed the alt text.
9c9328eca2
ccb68110d9
And a bug.
The compare button is bigger than normal time.
@n0toose
Hey?
There is an easier pathway to reach the settings via "Enable more" at the end of the tab list if releases aren't enabled, yet. But, IMO, that is not preventing this PR to be merged.
@mahlzahn wrote in #597 (comment):
There is an easier pathway to reach the settings via "Enable more" at the end of the tab list if releases aren't enabled, yet. But, IMO, that is not preventing this PR to be merged.
@mahlzahn
Where is Enable more?
@Gnu1 wrote in #597 (comment):
@mahlzahn wrote in #597 (comment):
There is an easier pathway to reach the settings via "Enable more" at the end of the tab list if releases aren't enabled, yet. But, IMO, that is not preventing this PR to be merged.
@mahlzahn Where is
Enable more?
See in the attachement (on mobile).
I haven't Enable more tab!
@mahlzahn
I haven't Enable more tab!
Have you disabled repository unit suggestions?
@n0toose wrote in #597 (comment):
I haven't Enable more tab!
Have you disabled repository unit suggestions?
Yes. Ok.
@mahlzahn Hey, sorry - do you still think that this is good to merge given the context above?
@n0toose wrote in #597 (comment):
@mahlzahn Hey, sorry - do you still think that this is good to merge given the context above?
:/
Which context?
If you mean Enable more. It is not enabled in all repos. The way(from the Settings) is a definitive solution
If you mean Enable more. It is not enabled in all repos. The way(from the Settings) is a definitive solution
You're right, I had some trouble understanding you there. I'll approve the CI pipeline and merge if it passes.
Deployment of preview was successful: https://Codeberg-Documentation-pr-597.surge.sh
CI failure (links) appears to be irrelevant with this PR.
@n0toose wrote in #597 (comment):
@mahlzahn Hey, sorry - do you still think that this is good to merge given the context above?
As @Gnu1 said, yes. It's fine for me. The screenshot doesn't really follow the Codeberg docs design guidelines (with ice bear knut as user), but if OK for others, go ahead and merge.
I thnik the alt text is very good.
Sorry, I reviewed the new version but then briefly forgot that I reviewed it when dismissing my previous review. It's a chaotic day - but yeah, you're right, it's way better than before.
Gnu >>>>>>>>> ice bear knut
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?