by Angel Leon. March 17, 2015;
Last update on December 14, 2023
Updated on February 27, 2023
Updated August 29, 2019.
There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore
is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules
directory) as well as files that are generated (and regenerated) as artifacts of a build process.
All other files should be in your own global gitignore file:
.gitignore
in your home directory and add any filepath patterns you want to ignore.Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute
.config/git/ignore
for.gitignore
in your home directory, if you prefer.
# This is the simplest definition, with the addition of a type | |
input { | |
udp { | |
port => 25826 # Must be specified. 25826 is the default for collectd | |
buffer_size => 1452 # Should be specified. 1452 is the default for recent versions of collectd | |
codec => collectd { } # This will invoke the default options for the codec | |
type => "collectd" | |
} | |
} |
git branch -m old_branch new_branch # Rename branch locally | |
git push origin :old_branch # Delete the old branch | |
git push --set-upstream origin new_branch # Push the new branch, set local branch to track the new remote |
awk 'BEGIN { t = 0; c = 0 } { if($10 ~ /[[:digit:]]/) { t = t + $10; c++; } } END { print t / c}' /var/log/httpd/access_log |
First get to the existing directory
$ cd my/folder/
Now start a new git repository
$ git init
Identify if the current elements on the directory are needed or not and add them to the .gitignore file. When ready...
$ vim .gitignore
When ready create the first commit on the server