Codeberg/Community
54
325
Fork
You've already forked Community
12

next release (v1.15) preview #430

Closed
opened 2021年04月28日 21:52:28 +02:00 by 6543 · 9 comments
Be aware of: * [public static assets moved from root to `/assets`](https://github.com/go-gitea/gitea/pull/15219) * [Use a generic markup class to display externally rendered files and diffs #15735](https://github.com/go-gitea/gitea/pull/15735) * User now kann set user fisibility to private -> https://github.com/go-gitea/gitea/pull/16271 (limit it to "public" & "limited") Fix: * #142 * #341 * #135 ? * #163 * https://codeberg.org/Codeberg/build-deploy-gitea/issues/58 * #401 * #416 * #306 * #206 * #244 * #487 * #490
Owner
Copy link

With the assets path change, all pointers need to be updated. I know of https://codeberg.org/Codeberg/blog/src/branch/master/pelicanconf.py#L9 - something else in addition to the Gitea templates (that are already updated)?

With the assets path change, all pointers need to be updated. I know of https://codeberg.org/Codeberg/blog/src/branch/master/pelicanconf.py#L9 - something else in addition to the Gitea templates (that are already updated)?
Owner
Copy link

@rwa in the past, we just edited the post here to include the issues. Is the block / depends function easier to use?

@rwa in the past, we just edited the post here to include the issues. Is the block / depends function easier to use?

I'm not sure if it's easier to use, it's just another way of visualisation.
I think when browsing through the downstream issues it's easier to understand that it is "blocked" by the release issue instead of a generic event that "the issue has been mentioned in another issue" which might not necessarily mean it will be solved.

The only true reason why i used this feature is that i didn't realize i can edit your post. 😁

I'm not sure if it's easier to use, it's just another way of visualisation. I think when browsing through the downstream issues it's easier to understand that it is "blocked" by the release issue instead of a generic event that "the issue has been mentioned in another issue" which might not necessarily mean it will be solved. The only true reason why i used this feature is that i didn't realize i can edit your post. 😁
Owner
Copy link

the assets thing also means we have to move the robots.txt in build-deploy-gitea, as it currently only is available at /assets/robots.txt after an upgrade. Looks like we have to create a custom folder for it?
https://docs.gitea.io/en-us/search-engines-indexation/

https://codeberg-test.org/assets/robots.txt vs https://codeberg-test.org/robots.txt

the assets thing also means we have to move the robots.txt in build-deploy-gitea, as it currently only is available at /assets/robots.txt after an upgrade. Looks like we have to create a custom folder for it? https://docs.gitea.io/en-us/search-engines-indexation/ https://codeberg-test.org/assets/robots.txt vs https://codeberg-test.org/robots.txt
Author
Copy link

@fnetX this sounds like a serious issue for all gitea installs :/

@fnetX this sounds like a serious issue for all gitea installs :/
Owner
Copy link

It should at least be prominently stated in the Changelog / Release Notes!

It should at least be prominently stated in the Changelog / Release Notes!
Owner
Copy link

https://codeberg-test.org footer on codeberg-test still has the API link (was intentionally removed from previous versions, but might be useful?) and a link to the Gitea "Website" - something we might want to remove?

https://codeberg-test.org footer on codeberg-test still has the API link (was intentionally removed from previous versions, but might be useful?) and a link to the Gitea "Website" - something we might want to remove?
Author
Copy link

@fnetX I did add API link back intentionally - it was requested (Codeberg/build-deploy-gitea#58)

@fnetX I did add API link back intentionally - it was requested (https://codeberg.org/Codeberg/build-deploy-gitea/issues/58)
Owner
Copy link

Ah ... yeah I know about this issue, didn't notice you acted on purpose :-)
Thank you ... so only removing this website link? Let's not forget this :-)

Ah ... yeah I know about this issue, didn't notice you acted on purpose :-) Thank you ... so only removing this website link? Let's not forget this :-)
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Codeberg/Community#430
Reference in a new issue
Codeberg/Community
No description provided.
Delete branch "%!s()"

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?