scmuser created the topic: Git Certification and Course
Hi,
Could you please let me know the Certifications in GIT or GITHUB?
Category: Version Control Systems
GitLab is not responding
rajeshkumar created the topic: GitLab is not responding
Issues –
After setting up the gitlab in ubantu by following www.scmgalaxy.com/111-git/888-setting-up…n-local-machine.html
I am getting error called “GitLab is not responding” on front page.
Followup –
I did run status commands and got following output…
sudo gitlab-ctl status
run: nginx: (pid 12728) 165s; run: log: (pid 12574) 372s
run: postgresql: (pid 12731) 165s; run: log: (pid 12485) 421s
run: redis: (pid 12741) 165s; run: log: (pid 12402) 427s
run: sidekiq: (pid 12744) 165s; run: log: (pid 12558) 378s
run: unicorn: (pid 12808) 28s; run: log: (pid 12546) 380s
I stop and restart the gitlab using…
sudo gitlab-ctl start
ok: run: nginx: (pid 12961) 0s
ok: run: postgresql: (pid 12964) 0s
ok: run: redis: (pid 12967) 0s
ok: run: sidekiq: (pid 12970) 0s
ok: run: unicorn: (pid 12983) 0s
Solution
I found out that some other services was running with port 80. I just stopped that services and re-startted the gitlab services and it went through..
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
The ova package name does not match
rajeshkumar created the topic: the ova package name does not match
While importing github-enterprise-11.10.320-x86_64.ova in Vmware workstation 7, I am getting following error…
The ova package name does not match
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
rajeshkumar replied the topic: the ova package name does not match
Downloaded a OVA file and tried to import it into my VMWare Workstation and if something can go wrong – it does.
“the ova package name does not match the ovf file inside it” was the error message, after some searching I found out that a OVA is nothing else than a compressed tar file with another ending but includes the OVF and VHD files.
Usind 7-zip to look into it I found the name of the OVF and renamed the OVA to the same name – voila – it works
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
rajeshkumar replied the topic: the ova package name does not match
Another way – enterprise.github.com/help/articles/gett…rted-with-virtualbox
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
How to take Gitlab backup
rajeshkumar created the topic: How to take Gitlab backup
#!/bin/bash
sudo -u git -H /home/git/bin/gitlab-backup.sh
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
GitLab: You are not allowed to access develop!
rajeshkumar created the topic: remote: GitLab: You are not allowed to access develop!
Issues –
remote: GitLab: You are not allowed to access develop!
remote: error: hook declined to update refs/heads/develop To gitlab.corp.intuit.net/sbfs/qbo-mumble.git
! [remote rejected] develop -> develop (hook declined)
error: failed to push some refs to ‘ gitlab.corp.intuit.net/sbfs/qbo-mumble.git ‘
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
Why GIT differnece than another SCM?
rajeshkumar created the topic: Why GIT differnece than another SCM?
Why GIT differnece than another SCM?
Cheap Local Branching
Everything is Local
Git is Fast
Git is Small
The Staging Area
Distributed
Any Workflow
Easy to Learn
Git is the new standard
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
What does commit object contain and What is SHA1?
rajeshkumar created the topic: What does commit object contain and What is SHA1?
The SHA
All the information needed to represent the history of a project is stored in files referenced by a 40-digit “object name” that looks something like this:
6ff87c4664981e4397625791c8ea3bbb5f2279a3
You will see these 40-character strings all over the place in Git. In each case the name is calculated by taking the SHA1 hash of the contents of the object. The SHA1 hash is a cryptographic hash function. What that means to us is that it is virtually impossible to find two different objects with the same name. This has a number of advantages; among others:
Git can quickly determine whether two objects are identical or not, just by comparing names. Since object names are computed the same way in every repository, the same content stored in two repositories will always be stored under the same name. Git can detect errors when it reads an object, by checking that the object’s name is still the SHA1 hash of its contents.
The Objects
Every object consists of three things – a type, a size and content. The size is simply the size of the contents, the contents depend on what type of object it is, and there are four different types of objects: “blob”, “tree”, “commit”, and “tag”.
A “blob” is used to store file data – it is generally a file.
A “tree” is basically like a directory – it references a bunch of other trees and/or blobs (i.e. files and sub-directories)
A “commit” points to a single tree, marking it as what the project looked like at a certain point in time. It contains meta-information about that point in time, such as a timestamp, the author of the changes since the last commit, a pointer to the previous commit(s), etc.
A “tag” is a way to mark a specific commit as special in some way. It is normally used to tag certain commits as specific releases or something along those lines.
Almost all of Git is built around manipulating this simple structure of four different object types. It is sort of its own little filesystem that sits on top of your machine’s filesystem.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
Git Reset Vs Git Revert
rajeshkumar created the topic: git reset Vs git revert
git reset Vs git revert
The git revert command undoes a committed snapshot. But, instead of removing the commit from the project history, it figures out how to undo the changes introduced by the commit and appends a new commit with the resulting content. This prevents Git from losing history, which is important for the integrity of your revision history and for reliable collaboration.
git revert
Reverting vs. Resetting
It’s important to understand that git revert undoes a single commit—it does not “revert” back to the previous state of a project by removing all subsequent commits. In Git, this is actually called a reset, not a revert.\
Reverting has two important advantages over resetting. First, it doesn’t change the project history, which makes it a “safe” operation for commits that have already been published to a shared repository. For details about why altering shared history is dangerous, please see the git reset page.
Second, git revert is able to target an individual commit at an arbitrary point in the history, whereas git reset can only work backwards from the current commit. For example, if you wanted to undo an old commit with git reset, you would have to remove all of the commits that occurred after the target commit, remove it, then re-commit all of the subsequent commits. Needless to say, this is not an elegant undo solution.
git reset
If git revert is a “safe” way to undo changes, you can think of git reset as the dangerous method. When you undo with git reset(and the commits are no longer referenced by any ref or the reflog), there is no way to retrieve the original copy—it is a permanent undo. Care must be taken when using this tool, as it’s one of the only Git commands that has the potential to lose your work.
Usage
git reset
Remove the specified file from the staging area, but leave the working directory unchanged. This unstages a file without overwriting any changes.
git reset
Reset the staging area to match the most recent commit, but leave the working directory unchanged. This unstages all files without overwriting any changes, giving you the opportunity to re-build the staged snapshot from scratch.
git reset –hard
Reset the staging area and the working directory to match the most recent commit. In addition to unstaging changes, the –hard flag tells Git to overwrite all changes in the working directory, too. Put another way: this obliterates all uncommitted changes, so make sure you really want to throw away your local developments before using it.
git reset
Move the current branch tip backward to
git reset –hard
Move the current branch tip backward to
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
rajeshkumar replied the topic: git reset Vs git revert
More Reference —
www.atlassian.com/git/tutorial/undoing-changes#!revert
www.atlassian.com/git/tutorial/undoing-changes#!reset
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
What is Staging Area?
rajeshkumar created the topic: What is staging area?
The Git directory is where Git stores the metadata and object database for your project. This is the most important part of Git, and it is what is copied when you clone a repository from another computer.
The working directory is a single checkout of one version of the project. These files are pulled out of the compressed database in the Git directory and placed on disk for you to use or modify.
The staging area is a simple file, generally contained in your Git directory, that stores information about what will go into your next commit. It’s sometimes referred to as the index, but it’s becoming standard to refer to it as the staging area.
The basic Git workflow goes something like this:
You modify files in your working directory.
You stage the files, adding snapshots of them to your staging area.
You do a commit, which takes the files as they are in the staging area and stores that snapshot permanently to your Git directory.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn
How to clean workspace in git?
rajeshkumar created the topic: How to clean workspace in git?
To reset a specific file to the last-committed state (to discard uncommitted changes in a specific file):
git checkout thefiletoreset.txt
This is mentioned in the git status output:
(use “git checkout —
To reset the entire repository to the last committed state:
git reset –hard
To remove untracked files, I usually just delete all files in the working copy (but not the .git/ folder!), then do git reset –hard which leaves it with only committed files.
A better way is to use git clean:
git clean -d -x -f
will remove untracked files, including directories (-d) and files ignored by git (-x). Replace the -f argument with -n to perform a dry-run or -i for interactive mode and it will tell you what will be removed.
you delete local files from your current branch?
git clean -f
But beware… there’s no going back. Use -n or –dry-run to preview the damage you’ll do.
If you want to also remove directories, run git clean -f -d
If you just want to remove ignored files, run git clean -f -X
If you want to remove ignored as well as non-ignored files, run git clean -f -x
Note the case difference on the X for the two latter commands.
Regards,
Rajesh Kumar
Twitt me @ twitter.com/RajeshKumarIn