Changed pagure links to forge and updated screenshots #52

Merged
pbokoc merged 2 commits from jonashub/team-docs:forgejo-links into main 2026-04-06 17:12:19 +00:00
Member
No description provided.
modified:   modules/ROOT/assets/images/contrib-quickdocs/report-issue.png
	modified:   modules/ROOT/assets/images/contrib-quickdocs/watch-notification.png
	deleted:    modules/ROOT/assets/images/pagure-guide/assign-issues.png
	modified:   modules/ROOT/pages/contributing-docs/asciidoc-reusable-attributes.adoc
	modified:   modules/ROOT/pages/contributing-docs/contrib-quickdocs.adoc
	modified:   modules/ROOT/pages/contributing-docs/contributions-quick-repo-WITHDRAWN.adoc
	new file:   preview.pid
deleted:    modules/ROOT/assets/images/contrib-quickdocs/assign-issues.png
	modified:   modules/ROOT/pages/contributing-docs/tools-localenv-preview.adoc
	modified:   preview.pid
pbokoc approved these changes 2026-04-06 17:06:47 +00:00
Owner

Alright, this seems good for #50, though as part of fixing #47 we'll have to do a more thorough cleanup, including changing the name of the modules/ROOT/assets/images/pagure-guide/ directory and stuff like that.

Great work on the screenshots!

Alright, this seems good for #50, though as part of fixing #47 we'll have to do a more thorough cleanup, including changing the name of the `modules/ROOT/assets/images/pagure-guide/` directory and stuff like that. Great work on the screenshots!
pbokoc merged commit f3fd5bdccf into main 2026-04-06 17:12:19 +00:00
Owner

Oh, one thing. @jonashub when you're fixing an issue and open a PR for it, please remember to link the PR in the issue, and the issue in the PR. You usually do at least one but it's best to do both. It wasn't too important in this case, since this repo has only a couple open issues, but in a more active repo like Quick Docs it's a PITA to determine if a PR is supposed to be fixing an issue (and which one) or just providing a change without an issue.

Oh, one thing. @jonashub when you're fixing an issue and open a PR for it, please remember to link the PR in the issue, and the issue in the PR. You usually do at least one but it's best to do both. It wasn't too important in this case, since this repo has only a couple open issues, but in a more active repo like Quick Docs it's a PITA to determine if a PR is supposed to be fixing an issue (and which one) or just providing a change without an issue.
Author
Member

Yeah, sorry for that. I am gonna link it from now on.

Yeah, sorry for that. I am gonna link it from now on.
Sign in to join this conversation.
No description provided.