More details about installation on Win #99

Merged
lhinderberger merged 3 commits from ivan-paleo/Documentation:install-git into prepare-merge 1 year ago
  • Select components (icon, updates)
  • Choose credential helper
  • With screenshots
- Select components (icon, updates) - Choose credential helper - With screenshots

@ivan-paleo - Please comment in this PR once it is ready for review (because as far as I know, there's no notification when someone removes WIP from a PR title).

@ivan-paleo - Please comment in this PR once it is ready for review (because as far as I know, there's no notification when someone removes `WIP` from a PR title).
hw commented 1 year ago
Owner

[...] (because as far as I know, there's no notification when someone removes WIP from a PR title).

is this true? If so, this would make a nice feature request

> [...] (because as far as I know, there's no notification when someone removes `WIP` from a PR title). is this true? If so, this would make a nice feature request

@hw I think we should try that out - I'll remove and add the WIP again on this PR; please tell me if you received any notification.

@hw I think we should try that out - I'll remove and add the WIP again on this PR; please tell me if you received any notification.
lhinderberger changed title from WIP: More details about installation on Win to More details about installation on Win 1 year ago
lhinderberger changed title from More details about installation on Win to WIP: More details about installation on Win 1 year ago
hw commented 1 year ago
Owner

I only received the notification for your message

I only received the notification for your message
Feature Request is at https://github.com/go-gitea/gitea/issues/13190
Poster

I will now be able to finalize this article, but I have a question before:

During installation, you can tick a box to check for updates daily. Even though I checked it, I got no notification about the latest update (from 2.28.0 to 2.29.0).

I am not sure whether I should mention that Win10 users might not receive a notification.
What do you guys think?

I will now be able to finalize this article, but I have a question before: During installation, you can tick a box to check for updates daily. Even though I checked it, I got no notification about the latest update (from 2.28.0 to 2.29.0). I am not sure whether I should mention that Win10 users might not receive a notification. What do you guys think?

@ivan-paleo In my opinion, it would be better not to mention it. If it's a bug, it will get fixed eventually and then our docs would be out of date.

@ivan-paleo In my opinion, it would be better not to mention it. If it's a bug, it will get fixed eventually and then our docs would be out of date.
Poster

That's my opinion too. The only problem with that is that I have no idea how the notification looks like and if there is an updater or if you need to download the whole installer. But I can always edit later if needed.

That's my opinion too. The only problem with that is that I have no idea how the notification looks like and if there is an updater or if you need to download the whole installer. But I can always edit later if needed.

If I remember correctly, it's a notification in the Notification Center and you're directed to Git's website to download the installer for the new version. I'm not too sure though, it's been a while since I last had a Git update on Windows 😄

According to this article there's also the option to manually trigger a git update using git update-git-for-windows.

**If** I remember correctly, it's a notification in the Notification Center and you're directed to Git's website to download the installer for the new version. I'm not too sure though, it's been a while since I last had a Git update on Windows :smile: According to [this article](https://derekhackett.com/update-git-on-windows) there's also the option to manually trigger a git update using `git update-git-for-windows`.
Poster

Ah yes, let's try that out (but first revert to 2.28.0...)!

Ah yes, let's try that out (but first revert to 2.28.0...)!
ivan-paleo changed title from WIP: More details about installation on Win to More details about installation on Win 1 year ago
Poster

Ok, it's ready now.

But I cannot see all the files I've changed under commit... Is that normal? I've changed the MD files, and 2 PNGs files + their webP counterparts.

Also, nice surprise, it now displays PNG files before/after! Is that new or did I never notice it?

Ok, it's ready now. But I cannot see all the files I've changed under commit... Is that normal? I've changed the MD files, and 2 PNGs files + their webP counterparts. Also, nice surprise, it now displays PNG files before/after! Is that new or did I never notice it?

I cannot see the files in the changed files tab either. There, the indication is 5 changed files (in the tab header) but there's only one file visible. With my local clone I was able to confirm that the other files were successfully committed and pushed. So this looks like a Gitea bug to me.

I'll open an issue in Codeberg/Community for narrowing down the error -> Codeberg/Community#313

I cannot see the files in the changed files tab either. There, the indication is 5 changed files (in the tab header) but there's only one file visible. With my local clone I was able to confirm that the other files were successfully committed and pushed. So this looks like a Gitea bug to me. I'll open an issue in Codeberg/Community for narrowing down the error -> Codeberg/Community#313
lhinderberger added the
Kind: Documentation
Status: Blocked
labels 1 year ago
6543 approved these changes 1 year ago
lhinderberger added
Status: Review
and removed
Status: Blocked
labels 1 year ago
lhinderberger requested changes 1 year ago
There are some steps for which you might have to pay attention:
1. Choose your editor:
1. Select Components:
Poster

Seeing that this kind of installer is fairly standardized on Windows and not specific to Git, I don't think we need to explain this step.

Seeing that this kind of installer is fairly standardized on Windows and not specific to Git, I don't think we need to explain this step.
ivan-paleo marked this conversation as resolved
If you want to keep all your settings, simply tick the box `Only show new options` in the installation wizard (see screenshots above). Here, "new options" refer to the options that were not available in the previous version.
If you ticked the box to check for updates during installation, Git will inform you that a new version is available.
Alternatively, at the command line, type:
`git update-git-for-windows`
Poster

Please use the same syntax as used for the macOS part of the documentation to ensure this is rendered as a code box.

Please use the same syntax as used for the macOS part of the documentation to ensure this is rendered as a code box.
Poster

(I'd just post it here, but AFAIK there is no way to post a markdown code block inside a markdown code block 😄)

(I'd just post it here, but AFAIK there is no way to post a markdown code block inside a markdown code block :smile:)
ivan-paleo marked this conversation as resolved
If you ticked the box to check for updates during installation, Git will inform you that a new version is available.
Alternatively, at the command line, type:
`git update-git-for-windows`
In these cases, just follow the steps to download and install the latest version.
Poster

Which cases and which steps are you refering to?

Which cases and which steps are you refering to?
ivan-paleo marked this conversation as resolved
`git update-git-for-windows`
In these cases, just follow the steps to download and install the latest version.
You can also download the installer from the Git website as explained above. Make sure that you run the new installer with the same rights (administrator or user) as for the original installation. If not, it will be installed twice and that will create a mess.
Poster

Good catch! Let's put the part about the possibility of a duplicate installation this into an info box.

Good catch! Let's put the part about the possibility of a duplicate installation this into an info box.
ivan-paleo marked this conversation as resolved
You can also download the installer from the Git website as explained above. Make sure that you run the new installer with the same rights (administrator or user) as for the original installation. If not, it will be installed twice and that will create a mess.
If you want to keep all your settings, simply tick the box `Only show new options` in the installation wizard (see screenshots above). Here, "new options" refer to the options that were not available in the previous, installed version.
Poster

Not sure if we really need this explanation.

Not sure if we really need this explanation.
Poster

I shortened it, but I think this doesn't hurt to mention how to keep all previous settings.

I shortened it, but I think this doesn't hurt to mention how to keep all previous settings.
ivan-paleo marked this conversation as resolved
Poster

Thanks for the feedback! It should be fixed now.

Thanks for the feedback! It should be fixed now.
lhinderberger approved these changes 1 year ago
lhinderberger left a comment

Thank you for the PR :)

lhinderberger changed target branch from master to prepare-merge 1 year ago
lhinderberger merged commit 37e97781bf into prepare-merge 1 year ago

It's merged and deployed! :)

It's merged and deployed! :)

Reviewers

6543 approved these changes 1 year ago
lhinderberger approved these changes 1 year ago
The pull request has been merged as 37e97781bf.
Sign in to join this conversation.
No Milestone
No Assignees
4 Participants
Notifications
Due Date

No due date set.

Loading…
There is no content yet.