-
Notifications
You must be signed in to change notification settings - Fork 12
/
README
102 lines (67 loc) · 2.8 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
countdown.opensuse.org
======================================================================
This repo contains svg template used on any counter we use in openSUSE infrastructure.
If you want to work on counter for a new distribution,(or any event) please
create a fork based on master, work on your fork and then send a pull request.
see below detailled instructions.
Work is published normally with cc-by-sa v3 licence
Leap 15.x LCP with fixes from victorhck
Leap 42.x victorhck
13.2 Zvezdana
12.x Marcus Moeller
11.x Jakub Steiner
======================================================================
Working with the repo in GitHub
------------------------------------
On github world : origin link to your forked repository, and we
standarized the name of the original to upstream by convention.
First, create a fork of openSUSE branding repo, here you have a guide:
https://help.github.com/articles/fork-a-repo
Then clone your fork in your PC:
git clone https://github.com/$YOUR_GITHUB_ACCOUNT/countdown.o.o.git
and add the original repository as remote:
cd countdown.o.o
git remote add upstream https://github.com/openSUSE/countdown.o.o.git
Fetch the original content and checkout/merge the branch you want to work on:
(advanced you can work on you own branch, but for simplicity here we will stick on master)
git fetch upstream
git checkout -b master
git merge upstream master
Now you can work with your local branch.
Add files, rename, remove etc ....
if you want to see the result you can render the png by running ./render.py output_dir on you
own computer.
to check what you've changed
git status
To commit your changes to your fork, do:
if you have untracked file ( shown as is with git status )
just add them with git -a
# Example
git status
# On branch master
# Your branch is ahead of 'origin/master' by 3 commits.
# (use "git push" to publish your local commits)
#
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
# README
# nothing added to commit but untracked files present (use "git add" to track)
git add README
Then to record your changes in the local repository
git commit -a -m "A useful description (eventually bnc#NR) describing what change"
(use -a if all the changes are relatives to the same commit)
Now time to update your fork on github
git push
Then you can create a pull request you have a guide here :
https://help.github.com/articles/creating-a-pull-request
If you want to sync with upstream changes, do a:
git fetch upstream
git merge upstream master
(this action is manually what git pull will do if setup)
Important files
===============
@tobedone
Need help?
==========
If you need help with the workflow and process, you can contact the following
people on opensuse-artwork mailing list