[Tiki-devel] How to create a limited Tiki clone repository

Hi Guys,

I felt this may be some good hints (and was a message I started nearly a
year ago)

How to create a Tiki repository on my computer that doesn't take too
much space.

Here's the trick :

How to create a limited Git repository :

In a shell...

1. Create a tiki folder

*mkdir tiki*

2. Change to the tiki folder
**

*cd tiki*

3. Create a empty git repo

*git init*

4. Add a remote for the main tiki repository
**

*remote rename origin gitlab*

5. Edit the /git/ config file so we can choose what we get
**

*geany / vim / nano .git/config*

inside block/["remote gitlab"]/

__

*replace*/
/

/fetch = +refs/heads/*:refs/remotes/gitlab/*/

master branch (*need this one for sure*):*
*

/fetch = +refs/heads/master:refs/remotes/gitlab/master/

*choose what branch we want (add each line as needed):*

release *22.x* :
//

/fetch = +refs/heads/22.x:refs/remotes/gitlab/22.x/

release *21.x* :

/fetch = +refs/heads/21.x:refs/remotes/gitlab/21.x/

release *20.x* :

/fetch = +refs/heads/20.x:refs/remotes/gitlab/20.x/

release *19.x* :

/fetch = +refs/heads/19.x:refs/remotes/gitlab/19.x/

release *18.x* :

/fetch = +refs/heads/18.x:refs/remotes/gitlab/18.x/

release *15.x* :

/fetch = +refs/heads/15.x:refs/remotes/gitlab/15.x/

release *12.x* :

/fetch = +refs/heads/12.x:refs/remotes/gitlab/12.x/

We configure to push the tags to our repository
//

*git config push.followTags true*

We add our own repository (replace [email protected]:polynamaude_ by your
own repository. Can also be a Github).

On Gitlab the repository will be created if inexistent, you need to make
sure it end with _.git_
**

*git remote add origin [email protected]
<mailto:[email protected]>:polynamaude/tiki.git*

We checkout to master
**

*git checkout master*

We push master and set it's upstream to origin
**

*git push –set-upstream origin master*

We create a personal branch to work on master

*git checkout -b wip/master*

We push this branch to our own repository. This way we can work on our
own "master" branch and merge later on.

*git push --set-upstream origin wip/master*

We checkout to branch 22.x
**

*git checkout 22.x*

We push to our personal repository
**

*git push –set-upstream origin 22.x*

We create a personal branch to work on 22.x

*git checkout -b wip/22.x*

We push this branch to our own repository.

We repeat this with all the branch we have decided to follow.

We can create many /wip/ branch for our own need and different project
we are working on. This simplify follow up of code modifications.

Example :

*git checkout master* (I want to add something new, so I start with
/master/)

*git checkout -b wip/master_worlddominationplugin* (Suggestion : use a
shorter name for usability)

*git push --set-upstream *(or -u) *origin* (my personal remote name)
*wip/master_worlddominationplugin* (my too long branch name)

By grouping personal branch under the /wip/ namespace I can use short
name without risking collision, also it's easy to remind to what they
correspond.



-- 
Polyna-Maude R.-Summerside
https://www.polynamaude.com/

-Be smart, Be wise, Support opensource development

*Mise en garde concernant la confidentialité*

La présente communication est confidentielle et transmise sous le sceau du
secret professionnel. Si vous n’êtes pas le destinataire visé ou son
mandataire chargé de lui transmettre cette communication, vous êtes par
les présentes avisées qu’il est expressément interdit d’en dévoiler la
teneur, de la copier, de la distribuer ou de prendre quelques mesures
fondées sur l’information qu’il y est contenu. Si vous aviez reçu cette
communication, par erreur, veuillez nous en aviser immédiatement par
téléphone (frais virés) et nous retourner l’original sans tirer ni garder
de copie, soit par la poste à l’adresse ci-haut mentionnée.

*Confidentiality Notice*

The information in this transmission may contain
privileged and confidential information and is intended only for the use
of the person or corporate entity to which it is addressed. The
confidential nature of this communication remains regardless of whether or
not you are an intended recipient. If you are not an intended recipient,
please notify the sender immediately and destroy this message and all
attachments, without making a copy. Any distribution or reproduction of
this message is prohibited. We assume no liability for the interception of
any Internet communication or the transmission of computer viruses.

/CP 99900 FJ 782 595
SUCC ST- DOMINIQUE
MONTRÉAL QC H2S 0E3
/

_______________________________________________
TikiWiki-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel