Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm packages: respect "repository" field to automatically set repository link of uploaded packages #20146

Closed
Mai-Lapyst opened this issue Jun 26, 2022 · 0 comments · Fixed by #20379
Labels
topic/packages type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@Mai-Lapyst
Copy link
Contributor

Mai-Lapyst commented Jun 26, 2022

Feature Description

npm packages allow for an "repository" field to add an link to an code repository; this could be used to automatically set the repository link of an package when uploading it.

Screenshots

No response

@Mai-Lapyst Mai-Lapyst added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels Jun 26, 2022
Mai-Lapyst added a commit to Mai-Lapyst/gitea that referenced this issue Mar 28, 2023
…the repository url present inside package.json; closes go-gitea#20146
jolheiser pushed a commit that referenced this issue Mar 28, 2023
…#20379)

automatically set repository link for package based on the repository
url present inside package.json

closes #20146
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
topic/packages type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants