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

Merge push to create, open PR from push, and push options docs articles into one #23744

Merged
merged 9 commits into from
Apr 6, 2023

Conversation

lunny
Copy link
Member

@lunny lunny commented Mar 27, 2023

Add documentation for this feature.

gitea-push-hint

@lunny lunny added the type/docs This PR mainly updates/creates documentation label Mar 27, 2023
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Apr 6, 2023
@delvh delvh added this to the 1.20.0 milestone Apr 6, 2023
@delvh delvh added the outdated/backport/v1.19 This PR should be backported to Gitea 1.19 label Apr 6, 2023
@delvh delvh changed the title Merge 2 push related documentations as 1 and added push merge hint Merge push to create, open PR from push, and push options docs articles into one Apr 6, 2023
docs/content/doc/usage/push.en-us.md Outdated Show resolved Hide resolved
docs/content/doc/usage/push.en-us.md Outdated Show resolved Hide resolved
@GiteaBot GiteaBot added lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. and removed lgtm/need 1 This PR needs approval from one additional maintainer to be merged. labels Apr 6, 2023
@delvh delvh added reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. and removed lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. labels Apr 6, 2023
@lunny lunny merged commit 8857e97 into go-gitea:main Apr 6, 2023
@lunny lunny deleted the lunny/push_hint branch April 6, 2023 23:36
@GiteaBot
Copy link
Contributor

GiteaBot commented Apr 6, 2023

I was unable to create a backport for 1.19. @lunny, please send one manually. 🍵

@GiteaBot GiteaBot added backport/manual No power to the bots! Create your backport yourself! lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. labels Apr 6, 2023
lunny added a commit to lunny/gitea that referenced this pull request Apr 6, 2023
…articles into one (go-gitea#23744)

Add documentation for this feature.

<img width="734" alt="gitea-push-hint"
src="https://user-images.githubusercontent.com/81045/227921177-af08ab76-7556-4a69-8da9-bb59cec1388b.png">

---------

Co-authored-by: delvh <[email protected]>
@lunny lunny removed the reviewed/wait-merge This pull request is part of the merge queue. It will be merged soon. label Apr 6, 2023
@lunny lunny added the backport/done All backports for this PR have been created label Apr 6, 2023
lunny added a commit that referenced this pull request Apr 7, 2023
zjjhot added a commit to zjjhot/gitea that referenced this pull request Apr 7, 2023
* upstream/main:
  Clean template/helper.go (go-gitea#23922)
  Remove `Repository.getFilesChanged` to fix Actions `paths` and `paths-ignore` filter (go-gitea#23920)
  Hardcode path to docker images (go-gitea#23955)
  Title can be empty when creating tag only (go-gitea#23917)
  Actions: Use default branch as ref when a branch/tag delete occurs (go-gitea#23910)
  Refactor authors dropdown (send get request from frontend to avoid long wait time) (go-gitea#23890)
  [skip ci] Updated translations via Crowdin
  Merge `push to create`, `open PR from push`, and `push options` docs articles into one (go-gitea#23744)
  Delete deleted release attachments immediately from storage (go-gitea#23913)
  More specific and unique feed name for NuGet install command template. (go-gitea#23889)
  Treat PRs with agit flow as fork PRs when triggering actions. (go-gitea#23884)
  Use graceful editorconfig loader to reduce errors when loading malformed editorconfigs (go-gitea#21257)
  Remove -v from vulncheck (go-gitea#23953)
  Improve permission check of packages (go-gitea#23879)
  Adjust some documentations titles (go-gitea#23941)
@yardenshoham
Copy link
Member

Can we somehow avoid referring to autogenerated files (trans-copy)?

Until today I was able to build the docs in Gitpod with

cd docs
make clean update
hugo server -D -F --baseUrl $(gp url 1313) --liveReloadPort=443 --appendPort=false --bind=0.0.0.0

I did it this way so no untracked (git) files would be created. Today, one of the pages is referring to an auto-generated page

In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet]({{< relref "doc/administration/config-cheat-sheet.zh-tw.md#repository-repository" >}}).
.

It seems the ability to automatically build the docs without generating files that don't have to get cleaned up before a commit is made was lost

@lunny
Copy link
Member Author

lunny commented Apr 7, 2023

Don't know whether we should ref to doc without .zh-tw here.

@go-gitea go-gitea locked as resolved and limited conversation to collaborators Aug 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport/done All backports for this PR have been created backport/manual No power to the bots! Create your backport yourself! lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. outdated/backport/v1.19 This PR should be backported to Gitea 1.19 type/docs This PR mainly updates/creates documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants