Help with Merge Request

training
1

I want to sent my solution and i have already read the Submission post it says that Solutions are sent through a Merge Request ( MR ) to the master branch of the repositories, also that i should only work on a branch whose name is exactly my username in Gitlab but i cant find my name, am i right? or, what i have to put in the source branch :face_with_head_bandage:

image
image.png1440×900 128 KB

2

Make sure you have created the branch
https://gitlab.com/autonomicmind/training/-/branches/active

if not, you must create it

1 Like
3

ok, i have to create a new brach named like my username, haven’t i? and from master, is it okey?

4

yes, that’s it, a new branch from master, and named like your username

1 Like
5

I see you’re new to git, the first step is to follow the widely documented guidelines in order to understand what are you doing and what you need to do to open a MR and send your challenges, I found these, but there are many many more:

I strongly recommend you to use (and learn how to use) the console line instead of the web interface for git, since there are too many checks on each commit and MR you send.

Once you’ve mastered git and concepts such as pull, push, commit ,rebase and squash I invite you to read again the submission criteria guidelines, I’m sure you’ll find interesting things that you didn’t see the first time, also you can check the accepted MRs in order to understand how a good commit must be structured.

I hope it helps :slight_smile:

2 Likes
6

okey i checked the accepted MRs and i feel better but i have a question, when i do my MR i have to attach my file in the description with the other information and the OTHERS links, or where?

7

You should take a better look to the guide @hermit-purple just posted, try to learn more about source management and how to upload files to a remote repository using git https://youtu.be/6pAXylqATB0 take a look at this guide, it’s for github but is the same thing for gitlab, you clone the repository locally and use a code editor to manage git and your files, i recommend Visual Studio Code.

8

i did all that you said before, and i have a problem when i write
$ git push -u origin master
it is an error
error: src refspec master does not match any
error: failed to push some refs to ‘https://gitlab.com/autonomicmind/training/’

9

You cannot push your changes directly to the master branch because it’s protected, you must first create your own branch (git checkout -b mybranch) modify your branch, commit your changes following the submission criteria and only then you can push your changes to your branch (git push origin mybranch) and open a MR.

10

now it sais

remote: HTTP Basic: Access denied
fatal: Authentication failed for ‘https://gitlab.com/autonomicmind/training.git/’

11

Please write the commands you are using and the outcome of such commands to have better understanding of the issue

12

Karinjo@Karinjo-PC MINGW64 /e/Autonomic (master)
$ git add Neuman.c

Karinjo@Karinjo-PC MINGW64 /e/Autonomic (master)
$ git commit -m “codeabbey, 24 (5.26)”
[master (root-commit) c9d507f] codeabbey, 24 (5.26)
2 files changed, 46 insertions(+)
create mode 100644 Neuman.c
create mode 160000 training

Karinjo@Karinjo-PC MINGW64 /e/Autonomic (karito1998)
$ git checkout -b karol1998
Switched to a new branch ‘karol1998’

Karinjo@Karinjo-PC MINGW64 /e/Autonomic (karol1998)
$ git remote add origin https://gitlab.com/autonomicmind/training/
fatal: remote origin already exists.

Karinjo@Karinjo-PC MINGW64 /e/Autonomic (karol1998)
$ git push origin karol1998
remote: HTTP Basic: Access denied
fatal: Authentication failed for ‘https://gitlab.com/autonomicmind/training.git/’

13

Ok you have some issues here, not only in the commands but in the order you are using them. Here are some advices:

  1. First of all I suggest you to begin working in your branch since the begining, so the first command you should use is git checkout -b mybranch.

  2. After that you can set the upstream origin to origin/master, allowing you to keep the tracking of the master branch from your own branch by using git branch -u origin/master

  3. Once you have properly configured your branch, you are ready to modify the files and commit the changes, DO NOT add new origins in your branch, this only leads to malfunctions and misconfigurations of the git config files.

  4. Finally, when you finish your commit you can push your changes to the remote repository by using git push origin mybranch, if you check the remote repository in your browser in the section branches you’ll see your branch with the changes you applied, if everything goes well you are ready to open your first Merge Request

Keep in mind that you must update your local repository periodically, use git pull at least twice a day

2 Likes
14

@previous-bell If this topic is solved, please mark it as such
by checking the solution chart at the bottom of the post you
consider that properly answers your question.