jonashub/team-docs
1
0
Fork 0
forked from docs/team-docs
Code Pull requests Activity

web IDE fork sync issue milestone changed to GitLab release 15.11

Browse source
This commit is contained in:
hank L 2023-03-22 21:24:54 +00:00
commit a0570218da
1 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

4
modules/ROOT/pages/contributing-docs/tools-gitlab-howto.adoc
View file

@ -38,7 +38,7 @@ If you have already a GitLab account and want to link it to your Fedora account,
a|image::2-GitLabSignin.png[align="center",width=940,role=black-border]
|===
NOTE: From GitLab 15.7, a new Web IDE editor was introduced. This guide focuses on the new <<web-ide-editor,Web IDE editor>>.
NOTE: From GitLab 15.7, a new Web IDE was introduced. This guide focuses on the new Web IDE.
=== Launch Web IDE and fork the project
@ -66,7 +66,7 @@ If you have a forked repository (e.g., during an earlier contribution), you will
If you do not launch Web IDE from your fork, *edit fork in Web IDE* button will appear in lieu of the *Open in Web IDE* button. Then you will be prompted to *go to fork* and checkout to your fork.
CAUTION: If you have forked the repository before, and if you have already the related branch, GitLab will not check if your fork’s branch is up to date. It will forward you to the respective file in the related branch of your fork even if this file is no longer up to date. GitLab knows about the problem and it is planned to solve this problem with the 15.10 release by the end of March 2023.
CAUTION: If you have forked the repository before, and if you have already the related branch, GitLab will not check if your fork’s branch is up to date. It will forward you to the respective file in the related branch of your fork even if this file is no longer up to date. GitLab 15.11 release is expected to fix the issue by April 17 2023.
=== Write, preview, edit and repeat