I can do everything else I need but with the GUI I cannot seem to figure out how to pull or push code. Pushing is more important in this case, anyone know how?
Anyone looking for this feature in gitg 3.14: I got confirmation from a developer that it hasn't been implemented yet.
Figured it out, not too difficult, just have to right click on the branch name when you are looking at your commit history
On the history tab, right click on the name of the tracking branch
Create on .git/hooks a file named post-commit and insert this code
#!/bin/bash
git push -u origin master
and turn this into a executable script
chmod 755 post-commit
Push action is available starting from version 3.32.0
See NEWS file in "Release 3.32.0" gitg commit
According to the official project roadmap, it is a feature in todo state;
the target release is 0.3 so I assume this table it is not updated so this project is poorly maintained: we can imagine real gnome coders do not use GUIs :)
You have to clone a repository previously.
For example:
git clone https://github.com/manuelkiessling/NodeBeginnerBook.git
Once cloned, go into the downloaded repository and execute gitk
Related
enter image description here
I tried this, but there's an error
enter image description here
Error message says
No .platform/services.yaml file found in the repository.
No .platform/routes.yaml file found in the repository.
enter image description here
but It's definitely there.
i don't understand...
Without seeing your repository, my guess is that those two files haven't been committed to the repository (the ! next to each of them in your third image). You can double-check by doing git status. If they are definitely committed, hop into our slack workspace and/or submit a support ticket so we can take a look at what's happening.
It sounds like you use visual studio and you need to:
add the files to git
commit the files to git
push the file to platform.sh
If you have trouble with this, you may want to use one of the existing template https://docs.platform.sh/development/templates.html and the modify these files.
In general, it is easier to start from a functional solution than a non working one ;-)
in my new project I can't close Gitlab issue's automatically via commit. this is what I try to do:
git add .
git commit -m "close #32"
git push origin develop
in my previous project when I try this codes, issue closed automatically in Gitlab.
what should I do?
First, make sure the commit closing the issue is not the very first commit.
As documented in gitlab-org/gitlab-foss issue 54722, it would not work. By design.
Check if another new commit, with the same comment, works better.
If not, check the GitLab server log for any error mentioning a failure to process the commit comments.
Possibly the feature is disabled from GitLab for certain reason.
Go to GitLab -> Your Project -> Settings -> Repository and see the below screenshot. As seen, the checkbox needs to be enabled in order to avail the auto close functionality based on the reference in the commit message.
I have my project in Pycharm but I want to push the complete project on git in one go. Is there any way to do it
It is difficult to understand the exact problem. But you need to be a little more detailed so that we can understand the problem. In general, under the VCS you need to map the git repo where you want to push your code. Then you will get the option to push or pull under git suboption.
Try https://www.jetbrains.com/help/pycharm/commit-and-push-changes.html
How to do git commit, push and pull in builder?
I have not found any way to graphically do this through the IDE Builder.
Not possible yet. There is a feature request, and the Roadmap mentions the "Git Perspective":
We would like an additional “Git” perspective that can be used to
manage various source control aspects. You might use this to stage
files for commit. You might use it to browse your projects history
including searching for a previous commit to inspect it.
git GUI might help you or you have comes in the terminal no choice.
I have some projects set up on GitLab Cloud, complete with issues, wiki pages, etc. I've recently set up an internally hosted gitlab instance. I'd like to bring these projects over from GitLab Cloud to the internal GitLab instance.
Bringing over the git repos seems easy enough (change the remote and push), but I don't see how to bring over the wikis and issues.
In general it seems like this isn't possible. (There's a GitLab Feedback for it here.)
However, the project wiki's seem to be their own git repos, which you can see on the Git Access tab. While that doesn't solve issues/snippets, it gets you part of the way there.
I don't know how to transfer over issues as I have not had to do that yet, but passing over the wiki is not that difficult.
On your old gitlab instance you will notice two repositories for your project (let's pretend your wiki is oldproject), one will say something like oldproject.git and oldproject.wiki.git.
The general path to the repositories where you can see the names I am talking about (let's assume user-name is "myaccount") can be found here:
/home/git/repositories/myaccount/
or (if using the omnibus installer):
/var/opt/gitlab/git-data/repositories/myaccount/
I presume you already know how to transfer over oldproject.git. You do the exact same thing with the wiki, only you create a bundle file out of oldproject.wiki.git:
git clone http://gitlab-instance-ip/user-name/oldproject.wiki.git
cd oldproject.wiki
git bundle create oldproject-wiki.bundle --all
Now initialize your new project in gitlab...I presume you already know how to do that as you suggested in your question that you know how to import the files from your project over to the new instance without problem. Now repeat for the wiki:
git clone http://new-gitlab-ip/user-name/newproject.wiki.git
cd newproject.wiki
git pull /path/to/oldproject-wiki.bundle
git push -u origin master
I had a very similar problem to yours where I didn't see that anything was actually "pushed". When I went back to the gitlab project I noticed that it was in fact updated with the wiki. See here if you think it will help: Importing Gitlab Wiki to a new Gitlab Instance
Good luck!