Skip to content

Add FAQ for version downloads #6742

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

Merged
merged 3 commits into from
Apr 24, 2019
Merged

Add FAQ for version downloads #6742

merged 3 commits into from
Apr 24, 2019

Conversation

jolheiser
Copy link
Member

This is probably the single most asked question, I'm not sure how I missed it on my first FAQ pass. 😂
This topic is covered in our CONTRIBUTING.md, however I don't think that's where people would naturally go to look for this kind of information.

If there is anything else that should be included in this pass of the FAQ, please let me know.

Signed-off-by: jolheiser <[email protected]>
Signed-off-by: jolheiser <[email protected]>
@GiteaBot GiteaBot added the lgtm/need 1 This PR needs approval from one additional maintainer to be merged. label Apr 24, 2019
Copy link
Member

@mrsdizzie mrsdizzie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Somewhat related to this but not blocking -- Can we use variables in the docs so that a similar page like https://docs.gitea.io/en-us/install-from-binary/ can use wget -O gitea https://dl.gitea.io/gitea/$latest_stable/gitea-$latest_stable-linux-amd64 and it would be possible to have text in the docs that reference the latest stable release without being out of date?

Would be nice if this section could also have "The current recommended release is $gitea_stable and available here" without needing to be updated.

@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 24, 2019
@jolheiser
Copy link
Member Author

jolheiser commented Apr 24, 2019

@mrsdizzie I like that idea, however I think that's just another thing to remember to change when we have a new release and documentation is already prone to being out of date.

(Also not sure if Hugo supports that within the markdown files)
Looks like we would need to add our own custom shortcode to make this work.

@lunny lunny added the type/docs This PR mainly updates/creates documentation label Apr 24, 2019
@codecov-io
Copy link

Codecov Report

Merging #6742 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #6742      +/-   ##
==========================================
- Coverage   40.82%   40.81%   -0.02%     
==========================================
  Files         421      421              
  Lines       57902    57902              
==========================================
- Hits        23640    23631       -9     
- Misses      31123    31133      +10     
+ Partials     3139     3138       -1
Impacted Files Coverage Δ
models/unit.go 45.71% <0%> (-5.72%) ⬇️
modules/log/event.go 64.46% <0%> (-1.53%) ⬇️
routers/repo/view.go 41.6% <0%> (-1.01%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 1d8b521...0265ab6. Read the comment docs.

@techknowlogick techknowlogick merged commit 6a58832 into go-gitea:master Apr 24, 2019
@jolheiser jolheiser deleted the faq branch April 24, 2019 18:45
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lgtm/done This PR has enough approvals to get merged. There are no important open reservations anymore. type/docs This PR mainly updates/creates documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants