From 083099c38f4a059fb9607628fb902c802d9bfb73 Mon Sep 17 00:00:00 2001 From: U Phuyal Date: Mon, 3 Mar 2025 22:14:04 +0000 Subject: [PATCH 1/3] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 9694462..fe6b51a 100644 --- a/README.md +++ b/README.md @@ -29,11 +29,11 @@ On the trial repository, in the top right, select the vertical ellipsis and sele Note this step is essential for all others below, and you would have to wait for someone to approve your request before following the remaining steps. -On the trial repository in the top right, select “Edit” and then “Open in Web IDE”. The editor view will open. On the left side menu, one can navigate through the files in the trial and modify multiple ones. These modifications will be marked in the left side bar with branch icon (called “source control”). For instance, in the depicted example below two modifications were done (one in Connection Setup.mb and one in System Information.md) and those are marked by the number two on the branch icon. +On the trial repository in the top right, select “Edit” and then “Open in Web IDE”. The editor view will open. On the left side menu, one can navigate through the files in the trial and modify multiple ones. These modifications will be marked in the left side bar with branch icon (called “source control”). For instance, in the depicted example below two modifications were done (one in Connection Setup.md and one in System Information.md) and those are marked by the number two on the branch icon. ![](./figures/edit_view.png) -When all the modifications are done, one can click on the branch icon and see all the changes performed. Under “Commit message” write a one sentence summary of your CR. Then on the right of “Commit and push to ‘main’”, one can click on the down arrow icon and an option should appear to “Commit to new branch”. Once that option is clicked you should write the name of the new branch i.e. a CR tittle (note that there should be no spaces between words names, - can be used instead e.g. this-is-the-CR-tittle). +When all the modifications are done, one can click on the branch icon and see all the changes performed. Under “Commit message” write a one sentence summary of your CR. Then on the right of “Commit and push to ‘main’”, one can click on the down arrow icon and an option should appear to “Commit to new branch”. Once that option is clicked you should write the name of the new branch i.e. a CR tittle (note that there should be no spaces between words names, - can be used instead e.g. this-is-the-CR-title). ![](./figures/commit_view.png) -- GitLab From 7daf4c0e0b44f33d0cfbf53b949f5637408cb981 Mon Sep 17 00:00:00 2001 From: U Phuyal Date: Mon, 3 Mar 2025 22:19:56 +0000 Subject: [PATCH 2/3] Further update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index fe6b51a..9a24472 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ On the trial repository in the top right, select “Edit” and then “Open in ![](./figures/edit_view.png) -When all the modifications are done, one can click on the branch icon and see all the changes performed. Under “Commit message” write a one sentence summary of your CR. Then on the right of “Commit and push to ‘main’”, one can click on the down arrow icon and an option should appear to “Commit to new branch”. Once that option is clicked you should write the name of the new branch i.e. a CR tittle (note that there should be no spaces between words names, - can be used instead e.g. this-is-the-CR-title). +When all the modifications are done, one can click on the branch icon and see all the changes performed. Under “Commit message” write a one sentence summary of your CR. Then on the right of “Commit and push to ‘main’”, one can click on the down arrow icon and an option should appear to “Commit to new branch”. Once that option is clicked you should write the name of the new branch i.e. a CR title (note that there should be no spaces between words names, - can be used instead e.g. this-is-the-CR-title). ![](./figures/commit_view.png) -- GitLab From e712e4d52e581761282bf0978e57ef59b64df33c Mon Sep 17 00:00:00 2001 From: "Umesh (Qualcomm)" Date: Fri, 7 Mar 2025 02:19:20 +0000 Subject: [PATCH 3/3] Apply 1 suggestion(s) to 1 file(s) Co-authored-by: Mattias Bergstrom (Ericsson) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9a24472..b211f0e 100644 --- a/README.md +++ b/README.md @@ -37,7 +37,7 @@ When all the modifications are done, one can click on the branch icon and see al ![](./figures/commit_view.png) -After this step, on the right bottom of the screen it should appear an option to create a merge request “Create MR”. When clicked, this will lead to the merge request view where you can fill in details similar as done in [the first CR](https://forge.3gpp.org/rep/bergstromm/ran2_trial/-/merge_requests/3) (merge request) we provided as example (e.g. the “Description” field and “Labels” could be filled in). +After this step, on the bottom right of the screen it should appear an option to create a merge request “Create MR”. When clicked, this will lead to the merge request view where you can fill in details similar as done in [the first CR](https://forge.3gpp.org/rep/bergstromm/ran2_trial/-/merge_requests/3) (merge request) we provided as example (e.g. the “Description” field and “Labels” could be filled in). Once done filling in the merge request details, click on “Create merge request” at bottom left. -- GitLab