You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue covers some process improvements to make it easier to submit and manage docs issues. PRs for docs or website improvement should still be filed against the website repo, but it would be easier to manage docs issues and prioritize them with other dev work if the issues are all in the same repo.
Describe the solution you'd like
Disable the website repo to accepting new issues, have all docs related issues filed agains the core harbor repo (this repo)
Migrate all open issues from the website repo to this repo (or close the ones that it doesn't make sense to move)
Create an issue template for docs that captures information needed to update docs or make site improvements and adds the area/docs label by default
Update website repo to require PRs to have at least 1 approving review before merging
There is also a PR open to add a PR template to the repo to help collect information on things like the changes being submitted issue(s) being fixed, #14271
The text was updated successfully, but these errors were encountered:
Looking closer at this, the maintainers are using milestones within the harbor repo for sprint planning, which only works with issues within that repo: https://github.com/goharbor/harbor/milestones
So, there might be a disconnect between the org board and the repo milestones? @renmaosheng Can you chime in here?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Is your feature request related to a problem? Please describe.
Docs for the Harbor project are kept in the https://github.com/goharbor/website repo.
This issue covers some process improvements to make it easier to submit and manage docs issues. PRs for docs or website improvement should still be filed against the website repo, but it would be easier to manage docs issues and prioritize them with other dev work if the issues are all in the same repo.
Describe the solution you'd like
There is also a PR open to add a PR template to the repo to help collect information on things like the changes being submitted issue(s) being fixed, #14271
The text was updated successfully, but these errors were encountered: