Joomla! Documentation - User contributions [en]

Administrator (User)/pt-br

2017-05-17T02:49:12Z

Juliano.freitas: Created page with "* Administrador * Super Usuário"

<noinclude><languages /></noinclude>

O Joomla! mantém duas classificações principais de grupos de usuários. As classificações são, principalmente grupos de usuários '''[[S:MyLanguage/Front-end|Front-end (site)]]''' e '''[[S:MyLanguage/Back-end|Back-end (administração)]]'''. Usuários front-end só estão autorizados a fazer login usando o lado voltado para público do website. Usuários back-end estão autorizados a logar na parte administrativa do website. Como resultado, esses usuários também são chamados de usuários administrativos ou administradores.

Logins administrativos estão disponíveis por padrão em <code><nowiki>http://example.org/administrator</nowiki></code>.

===Usuários de back-end são ainda separados em 2 grupos===

* Administrador
* Super Usuário

The most privileged of these users belong to the Super Users group. Super Users have the highest privilege level and can make changes or add new features or content to any section of a Joomla! site.

===Points to note on Super Users===

* The default Super Users is 'admin' and is installed with every Joomla! site
* Super Users are able to log in on the Front-end or Back-end of the site
* A Joomla! site may have more than one designated Super Users

[[Category:Glossary]]
[[Category:Needs review]]

Translations:Administrator (User)/4/pt-br

2017-05-17T02:49:12Z

Juliano.freitas: Created page with "* Administrador * Super Usuário"

* Administrador
* Super Usuário

Administrator (User)/pt-br

2017-05-17T02:48:43Z

Juliano.freitas: Created page with "===Usuários de back-end são ainda separados em 2 grupos==="

<noinclude><languages /></noinclude>

O Joomla! mantém duas classificações principais de grupos de usuários. As classificações são, principalmente grupos de usuários '''[[S:MyLanguage/Front-end|Front-end (site)]]''' e '''[[S:MyLanguage/Back-end|Back-end (administração)]]'''. Usuários front-end só estão autorizados a fazer login usando o lado voltado para público do website. Usuários back-end estão autorizados a logar na parte administrativa do website. Como resultado, esses usuários também são chamados de usuários administrativos ou administradores.

Logins administrativos estão disponíveis por padrão em <code><nowiki>http://example.org/administrator</nowiki></code>.

===Usuários de back-end são ainda separados em 2 grupos===

* Administrator
* Super Users

The most privileged of these users belong to the Super Users group. Super Users have the highest privilege level and can make changes or add new features or content to any section of a Joomla! site.

===Points to note on Super Users===

* The default Super Users is 'admin' and is installed with every Joomla! site
* Super Users are able to log in on the Front-end or Back-end of the site
* A Joomla! site may have more than one designated Super Users

[[Category:Glossary]]
[[Category:Needs review]]

Translations:Administrator (User)/3/pt-br

2017-05-17T02:48:43Z

Juliano.freitas: Created page with "===Usuários de back-end são ainda separados em 2 grupos==="

===Usuários de back-end são ainda separados em 2 grupos===

Administrator (User)/pt-br

2017-05-17T02:47:59Z

Juliano.freitas: Created page with "Logins administrativos estão disponíveis por padrão em"

<noinclude><languages /></noinclude>

O Joomla! mantém duas classificações principais de grupos de usuários. As classificações são, principalmente grupos de usuários '''[[S:MyLanguage/Front-end|Front-end (site)]]''' e '''[[S:MyLanguage/Back-end|Back-end (administração)]]'''. Usuários front-end só estão autorizados a fazer login usando o lado voltado para público do website. Usuários back-end estão autorizados a logar na parte administrativa do website. Como resultado, esses usuários também são chamados de usuários administrativos ou administradores.

Logins administrativos estão disponíveis por padrão em <code><nowiki>http://example.org/administrator</nowiki></code>.

===Back-end users are further separated into 2 groups===

* Administrator
* Super Users

The most privileged of these users belong to the Super Users group. Super Users have the highest privilege level and can make changes or add new features or content to any section of a Joomla! site.

===Points to note on Super Users===

* The default Super Users is 'admin' and is installed with every Joomla! site
* Super Users are able to log in on the Front-end or Back-end of the site
* A Joomla! site may have more than one designated Super Users

[[Category:Glossary]]
[[Category:Needs review]]

Translations:Administrator (User)/2/pt-br

2017-05-17T02:47:59Z

Juliano.freitas: Created page with "Logins administrativos estão disponíveis por padrão em"

Logins administrativos estão disponíveis por padrão em

Administrator (User)/pt-br

2017-05-17T02:47:27Z

Juliano.freitas: Created page with "O Joomla! mantém duas classificações principais de grupos de usuários. As classificações são, principalmente grupos de usuários '''S:MyLanguage/Front-end|Front-end (..."

<noinclude><languages /></noinclude>

O Joomla! mantém duas classificações principais de grupos de usuários. As classificações são, principalmente grupos de usuários '''[[S:MyLanguage/Front-end|Front-end (site)]]''' e '''[[S:MyLanguage/Back-end|Back-end (administração)]]'''. Usuários front-end só estão autorizados a fazer login usando o lado voltado para público do website. Usuários back-end estão autorizados a logar na parte administrativa do website. Como resultado, esses usuários também são chamados de usuários administrativos ou administradores.

Administrative logins are available by default at <code><nowiki>http://example.org/administrator</nowiki></code>.

===Back-end users are further separated into 2 groups===

* Administrator
* Super Users

The most privileged of these users belong to the Super Users group. Super Users have the highest privilege level and can make changes or add new features or content to any section of a Joomla! site.

===Points to note on Super Users===

* The default Super Users is 'admin' and is installed with every Joomla! site
* Super Users are able to log in on the Front-end or Back-end of the site
* A Joomla! site may have more than one designated Super Users

[[Category:Glossary]]
[[Category:Needs review]]

Translations:Administrator (User)/1/pt-br

2017-05-17T02:47:27Z

O Joomla! mantém duas classificações principais de grupos de usuários. As classificações são, principalmente grupos de usuários '''[[S:MyLanguage/Front-end|Front-end (site)]]''' e '''[[S:MyLanguage/Back-end|Back-end (administração)]]'''. Usuários front-end só estão autorizados a fazer login usando o lado voltado para público do website. Usuários back-end estão autorizados a logar na parte administrativa do website. Como resultado, esses usuários também são chamados de usuários administrativos ou administradores.

Administrator (User)/pt-br

2017-05-17T02:42:17Z

Juliano.freitas: Created page with "Administrador (Usuário)"

<noinclude><languages /></noinclude>

Joomla! maintains two primary classifications of user groups. The classifications are primarily '''[[S:MyLanguage/Front-end|Front-end (site)]]''' and '''[[S:MyLanguage/Back-end|Back-end (administration)]]''' user groups. Front-end users are only allowed to log in using the public facing side of the website. Back-end users are allowed to log in on the administrative side of the web site. As a result these users are also referred to as administrative users, or admins.

Administrative logins are available by default at <code><nowiki>http://example.org/administrator</nowiki></code>.

===Back-end users are further separated into 2 groups===

* Administrator
* Super Users

The most privileged of these users belong to the Super Users group. Super Users have the highest privilege level and can make changes or add new features or content to any section of a Joomla! site.

===Points to note on Super Users===

* The default Super Users is 'admin' and is installed with every Joomla! site
* Super Users are able to log in on the Front-end or Back-end of the site
* A Joomla! site may have more than one designated Super Users

[[Category:Glossary]]
[[Category:Needs review]]

Translations:Administrator (User)/Page display title/pt-br

2017-05-17T02:42:16Z

Juliano.freitas: Created page with "Administrador (Usuário)"

Administrador (Usuário)

Translations:Accesslevel form field type/Page display title/pt-br

2017-05-17T02:41:31Z

Juliano.freitas: Created page with "Tipo de campo de formulário - Nível de Acesso"

Tipo de campo de formulário - Nível de Acesso

Accesslevel form field type/pt-br

2017-05-17T02:40:30Z

Juliano.freitas: Created page with "Fornece uma lista suspensa de opções de nível de acesso com a opção atual selecionada."

<noinclude><languages /></noinclude>
Fornece uma lista suspensa de opções de nível de acesso com a opção atual selecionada.

* '''nome''' (obrigatório) é o nome exclusivo do parâmetro.
* '''tipo''' (obrigatório) precisa ser ''nível de acesso''.
* '''rótulo''' (obrigatório) (traduzível) é o título descritivo do campo.
* '''descrição''' texto de descrição para o campo de formulário.
* '''classe''' classes adicionais para configuração de estilo.

Implementado por: libraries/joomla/form/fields/access.php

Exemplo de Definição XML:
<source type="xml">
<field name="access" type="accesslevel"
label="JFIELD_ACCESS_LABEL"
description="JFIELD_ACCESS_DESC"
class="span12 small" />
</source>

<noinclude>
[[Category:Standard form field types/pt-BR|Tipos de campo de formulário padrões]]
</noinclude>

Translations:Accesslevel form field type/1/pt-br

2017-05-17T02:40:30Z

Juliano.freitas: Created page with "Fornece uma lista suspensa de opções de nível de acesso com a opção atual selecionada."

Fornece uma lista suspensa de opções de nível de acesso com a opção atual selecionada.

Accesslevel form field type/pt-br

2017-05-17T02:39:49Z

Juliano.freitas: Created page with "* '''tipo''' (obrigatório) precisa ser ''nível de acesso''."

<noinclude><languages /></noinclude>
Provides a dropdown list of accesslevel options with the current option selected.

* '''nome''' (obrigatório) é o nome exclusivo do parâmetro.
* '''tipo''' (obrigatório) precisa ser ''nível de acesso''.
* '''rótulo''' (obrigatório) (traduzível) é o título descritivo do campo.
* '''descrição''' texto de descrição para o campo de formulário.
* '''classe''' classes adicionais para configuração de estilo.

Implementado por: libraries/joomla/form/fields/access.php

Exemplo de Definição XML:
<source type="xml">
<field name="access" type="accesslevel"
label="JFIELD_ACCESS_LABEL"
description="JFIELD_ACCESS_DESC"
class="span12 small" />
</source>

<noinclude>
[[Category:Standard form field types/pt-BR|Tipos de campo de formulário padrões]]
</noinclude>

Translations:Accesslevel form field type/3/pt-br

2017-05-17T02:39:48Z

Juliano.freitas: Created page with "* '''tipo''' (obrigatório) precisa ser ''nível de acesso''."

* '''tipo''' (obrigatório) precisa ser ''nível de acesso''.

Working with git and github/pt-br

2017-05-14T03:10:11Z

Juliano.freitas: Created page with "Category: Bug Squad/pt-br Category: Development/pt-br Category:GitHub/pt-br"

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

= Começando! =
== Cadastrar-se no GitHub e instalar o Git ==
Primeiro, você vai precisar se registrar no [http://www.github.com GitHub]. Isto é grátis e fácil de se fazer. Basta seguir os passos fornecidos.

Agora que estamos registrados, precisamos instalar o Git. A versão mais recente do Git pode ser encontrada em http://git-scm.com. Faça o download e abra o instalador. O Git é um programa CLI (Command Line Interface ou Interface de Linha Comando em Português). No início isso pode ser confuso e um pouco assustador, mas este documento irá guiá-lo através deste processo.

Se você não é um usuário avançado, apenas execute o instalador e precione os botões "próximo" até que o programa esteja instalado. O Git não danificará o seu sistema. Mais tarde você pode removê-lo como qualquer outro programa, se quiser.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Informação Extra=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad/pt-br]]
[[Category: Development/pt-br]]
[[Category:GitHub/pt-br]]
</noinclude>

Translations:Working with git and github/54/pt-br

2017-05-14T03:10:10Z

Juliano.freitas: Created page with "Category: Bug Squad/pt-br Category: Development/pt-br Category:GitHub/pt-br"

[[Category: Bug Squad/pt-br]]
[[Category: Development/pt-br]]
[[Category:GitHub/pt-br]]

Working with git and github/pt-br

2017-05-14T03:09:14Z

Juliano.freitas: Created page with "=Informação Extra="

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

= Começando! =
== Cadastrar-se no GitHub e instalar o Git ==
Primeiro, você vai precisar se registrar no [http://www.github.com GitHub]. Isto é grátis e fácil de se fazer. Basta seguir os passos fornecidos.

Agora que estamos registrados, precisamos instalar o Git. A versão mais recente do Git pode ser encontrada em http://git-scm.com. Faça o download e abra o instalador. O Git é um programa CLI (Command Line Interface ou Interface de Linha Comando em Português). No início isso pode ser confuso e um pouco assustador, mas este documento irá guiá-lo através deste processo.

Se você não é um usuário avançado, apenas execute o instalador e precione os botões "próximo" até que o programa esteja instalado. O Git não danificará o seu sistema. Mais tarde você pode removê-lo como qualquer outro programa, se quiser.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Informação Extra=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/50/pt-br

2017-05-14T03:09:13Z

Juliano.freitas: Created page with "=Informação Extra="

=Informação Extra=

Working with git and github/pt-br

2017-05-14T03:08:39Z

Juliano.freitas: Created page with "Se você não é um usuário avançado, apenas execute o instalador e precione os botões "próximo" até que o programa esteja instalado. O Git não danificará o seu sistema..."

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

= Começando! =
== Cadastrar-se no GitHub e instalar o Git ==
Primeiro, você vai precisar se registrar no [http://www.github.com GitHub]. Isto é grátis e fácil de se fazer. Basta seguir os passos fornecidos.

Agora que estamos registrados, precisamos instalar o Git. A versão mais recente do Git pode ser encontrada em http://git-scm.com. Faça o download e abra o instalador. O Git é um programa CLI (Command Line Interface ou Interface de Linha Comando em Português). No início isso pode ser confuso e um pouco assustador, mas este documento irá guiá-lo através deste processo.

Se você não é um usuário avançado, apenas execute o instalador e precione os botões "próximo" até que o programa esteja instalado. O Git não danificará o seu sistema. Mais tarde você pode removê-lo como qualquer outro programa, se quiser.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/11/pt-br

2017-05-14T03:08:38Z

Se você não é um usuário avançado, apenas execute o instalador e precione os botões "próximo" até que o programa esteja instalado. O Git não danificará o seu sistema. Mais tarde você pode removê-lo como qualquer outro programa, se quiser.

Working with git and github/pt-br

2017-05-14T03:06:51Z

Juliano.freitas: Created page with "Agora que estamos registrados, precisamos instalar o Git. A versão mais recente do Git pode ser encontrada em http://git-scm.com. Faça o download e abra o instalador. O Git..."

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

= Começando! =
== Cadastrar-se no GitHub e instalar o Git ==
Primeiro, você vai precisar se registrar no [http://www.github.com GitHub]. Isto é grátis e fácil de se fazer. Basta seguir os passos fornecidos.

Agora que estamos registrados, precisamos instalar o Git. A versão mais recente do Git pode ser encontrada em http://git-scm.com. Faça o download e abra o instalador. O Git é um programa CLI (Command Line Interface ou Interface de Linha Comando em Português). No início isso pode ser confuso e um pouco assustador, mas este documento irá guiá-lo através deste processo.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/10/pt-br

2017-05-14T03:06:51Z

Agora que estamos registrados, precisamos instalar o Git. A versão mais recente do Git pode ser encontrada em http://git-scm.com. Faça o download e abra o instalador. O Git é um programa CLI (Command Line Interface ou Interface de Linha Comando em Português). No início isso pode ser confuso e um pouco assustador, mas este documento irá guiá-lo através deste processo.

Working with git and github/pt-br

2017-05-14T03:04:55Z

Juliano.freitas: Created page with "Primeiro, você vai precisar se registrar no [http://www.github.com GitHub]. Isto é grátis e fácil de se fazer. Basta seguir os passos fornecidos."

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

= Começando! =
== Cadastrar-se no GitHub e instalar o Git ==
Primeiro, você vai precisar se registrar no [http://www.github.com GitHub]. Isto é grátis e fácil de se fazer. Basta seguir os passos fornecidos.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/9/pt-br

2017-05-14T03:04:55Z

Juliano.freitas: Created page with "Primeiro, você vai precisar se registrar no [http://www.github.com GitHub]. Isto é grátis e fácil de se fazer. Basta seguir os passos fornecidos."

Primeiro, você vai precisar se registrar no [http://www.github.com GitHub]. Isto é grátis e fácil de se fazer. Basta seguir os passos fornecidos.

Working with git and github/pt-br

2017-05-14T03:03:43Z

Juliano.freitas: Created page with "== Cadastrar-se no GitHub e instalar o Git =="

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

= Começando! =
== Cadastrar-se no GitHub e instalar o Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/8/pt-br

2017-05-14T03:03:43Z

Juliano.freitas: Created page with "== Cadastrar-se no GitHub e instalar o Git =="

== Cadastrar-se no GitHub e instalar o Git ==

Working with git and github/pt-br

2017-05-14T03:02:47Z

Juliano.freitas: Created page with "= Começando! ="

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

= Começando! =
== Sign up on GitHub and install Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/7/pt-br

2017-05-14T03:02:47Z

Juliano.freitas: Created page with "= Começando! ="

= Começando! =

Working with git and github/pt-br

2017-05-14T03:02:33Z

Juliano.freitas: Created page with "Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/jooml..."

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

= Getting Started =
== Sign up on GitHub and install Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/6/pt-br

2017-05-14T03:02:33Z

Joomla! usa GitHub e Git para manter seu código. Todos podem contribuir com o software Joomla!. A URL para o projeto Joomla! CMS no GitHub é: https://github.com/joomla/joomla-cms

Working with git and github/pt-br

2017-05-14T03:01:16Z

Juliano.freitas: Created page with "Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você..."

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Joomla! uses GitHub and Git to maintain its code. Everyone can contribute Joomla! software. The URL to the Joomla! CMS Project on GitHub is: https://github.com/joomla/joomla-cms

= Getting Started =
== Sign up on GitHub and install Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/5/pt-br

2017-05-14T03:01:15Z

Aqui está como o GitHub pode ser usado. [https://www.github.com GitHub] é um site que ajuda a gerenciar Projetos Git de forma visual. Como proprietário de um projeto, você pode alterar o código e comparar diferentes versões. Como usuário do projeto, você pode contribuir fazendo uma Requisição Pull. Uma Requisição Pull é uma solicitação para o proprietário puxar algum código para o projeto. Você está oferecendo um pedaço de código (talvez uma solução para um bug) e perguntando se o proprietário do projeto gostaria de usá-lo. Se o proprietário gostar, ele pode fundir (adicionar) ao seu projeto.

Working with git and github/pt-br

2017-05-14T02:58:25Z

Juliano.freitas: Created page with "O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você po..."

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Here is how GitHub can be used. [https://www.github.com GitHub] is an website that helps manage Git Projects in a visual way. As owner of a project you can change the code and compare different versions. As a user of the project you can contribute by making a Pull Requests. A pull request is a request to the owner to pull some code into the project. You're offering a piece of code (perhaps a solution for a bug) and asking if the Project owner would like to use it. If the owner likes it, he can merge (add) it to his project.

Joomla! uses GitHub and Git to maintain its code. Everyone can contribute Joomla! software. The URL to the Joomla! CMS Project on GitHub is: https://github.com/joomla/joomla-cms

= Getting Started =
== Sign up on GitHub and install Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/4/pt-br

2017-05-14T02:58:25Z

O Git é um sistema de controle de versão distribuído. É um sistema que registra alterações em arquivos e mantém essas alterações em um arquivo de histórico. Você pode sempre olhar para trás para uma versão anterior do seu código e restaurar as alterações, se quiser. Devido ao histórico do arquivo, o Git é muito útil quando você trabalha com muitas pessoas juntas no mesmo projeto.

Working with git and github/pt-br

2017-05-14T02:57:37Z

Juliano.freitas: Created page with "== O que são Git e GitHub? =="

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== O que são Git e GitHub? ==

Git is a distributed version control system. It is a system that records changes in files and keeps these changes in a history file. You can always look back to an earlier version of your code and restore changes if you like. Because of the history archive, Git is very useful when you work with many people together on the same project.

Here is how GitHub can be used. [https://www.github.com GitHub] is an website that helps manage Git Projects in a visual way. As owner of a project you can change the code and compare different versions. As a user of the project you can contribute by making a Pull Requests. A pull request is a request to the owner to pull some code into the project. You're offering a piece of code (perhaps a solution for a bug) and asking if the Project owner would like to use it. If the owner likes it, he can merge (add) it to his project.

Joomla! uses GitHub and Git to maintain its code. Everyone can contribute Joomla! software. The URL to the Joomla! CMS Project on GitHub is: https://github.com/joomla/joomla-cms

= Getting Started =
== Sign up on GitHub and install Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/3/pt-br

2017-05-14T02:57:37Z

Juliano.freitas: Created page with "== O que são Git e GitHub? =="

== O que são Git e GitHub? ==

Working with git and github/pt-br

2017-05-14T02:57:09Z

Juliano.freitas: Created page with "Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo ap..."

<noinclude><languages /></noinclude>

= Introdução =
Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

== What are Git and GitHub? ==

Git is a distributed version control system. It is a system that records changes in files and keeps these changes in a history file. You can always look back to an earlier version of your code and restore changes if you like. Because of the history archive, Git is very useful when you work with many people together on the same project.

Here is how GitHub can be used. [https://www.github.com GitHub] is an website that helps manage Git Projects in a visual way. As owner of a project you can change the code and compare different versions. As a user of the project you can contribute by making a Pull Requests. A pull request is a request to the owner to pull some code into the project. You're offering a piece of code (perhaps a solution for a bug) and asking if the Project owner would like to use it. If the owner likes it, he can merge (add) it to his project.

Joomla! uses GitHub and Git to maintain its code. Everyone can contribute Joomla! software. The URL to the Joomla! CMS Project on GitHub is: https://github.com/joomla/joomla-cms

= Getting Started =
== Sign up on GitHub and install Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/2/pt-br

2017-05-14T02:57:09Z

Este documento irá fornecer informações sobre como contribuir para o CMD Joomla! com a ajuda do Git e GitHub. Se você gosta de fazer uma alteração simples (um arquivo apenas), é mais fácil usar esta documentação: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Usando a interface do Github para Fazer Requisições Pull]]
Se você gosta de adicionar mudanças mais complexas ou está apenas interessado nisso, continue lendo!

Working with git and github/pt-br

2017-05-14T02:52:46Z

Juliano.freitas: Created page with "= Introdução ="

<noinclude><languages /></noinclude>

= Introdução =
This document will provide information about contributing to the Joomla! CMS with help of Git and GitHub. If you like to made a simple change (one file only), it is easier to use this documentation: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Using the Github UI to Make Pull Requests]]
If you like to add more complex changes or you're just interested in this, keep reading!

== What are Git and GitHub? ==

Git is a distributed version control system. It is a system that records changes in files and keeps these changes in a history file. You can always look back to an earlier version of your code and restore changes if you like. Because of the history archive, Git is very useful when you work with many people together on the same project.

Here is how GitHub can be used. [https://www.github.com GitHub] is an website that helps manage Git Projects in a visual way. As owner of a project you can change the code and compare different versions. As a user of the project you can contribute by making a Pull Requests. A pull request is a request to the owner to pull some code into the project. You're offering a piece of code (perhaps a solution for a bug) and asking if the Project owner would like to use it. If the owner likes it, he can merge (add) it to his project.

Joomla! uses GitHub and Git to maintain its code. Everyone can contribute Joomla! software. The URL to the Joomla! CMS Project on GitHub is: https://github.com/joomla/joomla-cms

= Getting Started =
== Sign up on GitHub and install Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/1/pt-br

2017-05-14T02:52:45Z

Juliano.freitas: Created page with "= Introdução ="

= Introdução =

Working with git and github/pt-br

2017-05-14T02:52:45Z

Juliano.freitas: Created page with "Trabalhando com git e github"

<noinclude><languages /></noinclude>

= Intro =
This document will provide information about contributing to the Joomla! CMS with help of Git and GitHub. If you like to made a simple change (one file only), it is easier to use this documentation: [[S:MyLanguage/Using the Github UI to Make Pull Requests|Using the Github UI to Make Pull Requests]]
If you like to add more complex changes or you're just interested in this, keep reading!

== What are Git and GitHub? ==

Git is a distributed version control system. It is a system that records changes in files and keeps these changes in a history file. You can always look back to an earlier version of your code and restore changes if you like. Because of the history archive, Git is very useful when you work with many people together on the same project.

Here is how GitHub can be used. [https://www.github.com GitHub] is an website that helps manage Git Projects in a visual way. As owner of a project you can change the code and compare different versions. As a user of the project you can contribute by making a Pull Requests. A pull request is a request to the owner to pull some code into the project. You're offering a piece of code (perhaps a solution for a bug) and asking if the Project owner would like to use it. If the owner likes it, he can merge (add) it to his project.

Joomla! uses GitHub and Git to maintain its code. Everyone can contribute Joomla! software. The URL to the Joomla! CMS Project on GitHub is: https://github.com/joomla/joomla-cms

= Getting Started =
== Sign up on GitHub and install Git ==
First, you will need to register at [http://www.github.com GitHub]. It's free and easy to do. Just follow the provided steps.

One we are signed up, we need to install Git. The latest version of Git can be found on http://git-scm.com. Download and open the installer. Git is an CLI (Command Line Interface) program. At the start this can be confusing and a bit scary but this document will lead you through the process.

If you're not an advanced user, just run the installer and press the "next" buttons until the program is installed. Git won't damage your system. Later you can remove it just like any other program if you like.

Once we installed Git, we open the program called "Git Bash." A command line will be opened. We're going to tell Git our name and email address. Git will use this information when we contribute to a project.
With the following commands we give Git that information:

<source>
git config --global user.name "Your name"
git config --global user.email youremail@mail.com
</source>

In the above commands, and all other commands given in this documentation, each line is a new command. So you type the fist line, press enter and then type the second line and press enter.

We are now ready to use Git and go farther with setting up our test installation.

=Setting up a test installation=
For our test installation we need a Web server program so that we can install and run Joomla! on our computer. There are a lot of programs that can do that such as [https://www.mamp.info/ MAMP] and [https://www.apachefriends.org/ XAMPP]. Download an install one of them.

After the installation of such a program (I use MAMP in this documentation), we going to install the latest version of Joomla!. In our case, the latest version of Joomla! is not the last stable release. The last version of Joomla! is the staging branch on GitHub.
First, let me explain a little bit more about GitHub.

== Fork and Clone Joomla! ==
On GitHub you can find projects, so called Repositories. Inside a project you might find several versions. Such a version is called a Branch. Joomla! has the following branches:
* '''Staging:''' This branch contains the latest bug fixes and new features of Joomla!
* '''Master:''' This branch is the current stable version of Joomla!
* '''3.5-dev''' This branch contains the files for Joomla! 3.5, which is not stable at this writing.

On our test location we going to use the '''Staging''' branch but if we should use this branch directly we have problem. We cannot modify this branch because we are not the owner of it.
We are going to make a copy of it. On GitHub this is called a Fork. We are the owner of that copy so we can modify it. After modifying we compare our fork with the original project. Then we can make a Pull Request for the changes we've made. More about that later.
You can Fork a branch by pressing the Fork button on the [https://github.com/joomla/joomla-cms Joomla! CMS Github Repository]. This button is located at the right top of the page.
[[File:Github-fork-button.png|none]]

After forking, we are going to install Joomla! on our local Web server. Go to the folder were you can run files on you Web server. Most of the program use a folder called <tt>htdocs</tt>. Once we are inside that folder, press the right mouse button an click on: "Git Bash Here". The command line will open for this location.

Type the following command to download the files from your Fork of the Joomla! CMS to your computer. Please replace username with the username you are using on GitHub.

<source>
git clone https://github.com/username/joomla-cms.git
</source>

For all commands given in this documentation, you have to open Git via the above described steps. Please remember that for other commands in this documentation.

Once Git is ready, open your browser and go to the installation on your localhost. Usually the URL is something like: <tt>http://localhost/joomla-cms</tt>. You will now see the default Joomla! installation process.

== Install Joomla! ==
The installation of Joomla! for our local test installation is almost the same as a regular installation. There are a two little differences.

For the database settings, the password and username are default. Most often the username is <tt>root</tt> and the password is also <tt>root</tt> or there is no password. If you still can't connect to the database, look in the manual for your local Web server for the username and password.

The last difference is the final step of the installation. Normally we must delete the installation folder to go further to the back-end or front-end of Joomla!. For a test installation we can skip this part and go directly to the back-end or front-end. Don't remove the installation folder. It can be very useful when we have to install Joomla again.

=Make Your Changes=
Now it is time to made our file changes to Joomla!. All changes we make will be registered and monitored by Git. At any moment you can type the command <tt>git status</tt> to see which files are modified or untracked. Untracked means that the file at that location is new for Git.

If you made a mistake or you would like to restore a file, use this command:

<source>
git checkout path/to/file
</source>

If you like to remove all changes you made, use the following commands:

<source>
git checkout .
git clean -f -d
</source>

The first command resets all files. The second command removes untracked files and folders.

==Publish Our Changes on GitHub==

=Push the Change to the Fork=
After making our changes, we have to upload our changes to our repository on GitHub. After that, we can make a pull request with our changes.

Uploading changes is called <tt>push</tt> in Git terms. Before we can do that, we have to do something very important. We must create a new branch for our changes. (A branch is a version of our project, remember?) If we don't do that and made our change directly to the staging branch, the first time there won't be a problem. But if we made changes for the second time, and the change we made the first time are not merged yet, all these changes will registered too as new changes.

So the first command we are going to run will create a new branch. It will prevent the above described problem.
Replace name-new-branch with the name of the new branch. This name must be short, and can only contain lower case letters and numbers. Do '''NOT''' use spaces. Instead of spaces, use - (minus).

<source>
git checkout -b name-new-branch
</source>

The next command tells git that all made changes are good, and are ready to commit.

<source>
git add --all
</source>

The following command adds our change to the branch. Please replace the message with a short description of your changes. This description will be the title of the pull request we are going to make.

<source>
git commit -m "description"
</source>

The final command will push (upload) the changes to our fork. Please replace name-new-branch with the name of the branch you made a few steps above.

<source>
git push origin name-new-branch
</source>

==Compare Forks and Make a Pull Request==
After pushing our change to GitHub, go to your fork of the Joomla! CMS.

=Extra information=
Because the staging version of Joomla! can change any moment, it is very useful to have the possibility for keeping our fork up-to-date. We can do that by adding a remote to our forked project:

<source>
git remote add upstream https://github.com/joomla/joomla-cms.git
</source>

We now added a remote called "upstream". With the following command, Git will search for new contribution (commits) in the staging branch we don't have in our fork. If it found some, it will add them to our fork:

<source>
git pull upstream staging
</source>

The changes are now only made on our local fork. To upload them to GitHub use the following command:

<source>
git push
</source>

<noinclude>
[[Category: Bug Squad]]
[[Category: Development]]
[[Category:GitHub]]
</noinclude>

Translations:Working with git and github/Page display title/pt-br

2017-05-14T02:52:44Z

Juliano.freitas: Created page with "Trabalhando com git e github"

Trabalhando com git e github

Adding a new user/pt-br

2017-05-12T03:03:52Z

Juliano.freitas: Created page with "Tutoriais Gerenciador de Usuários"

<noinclude><languages /></noinclude>
'''Adicionando um novo usuário'''

Um usuário é uma pessoa (ou grupo de pessoas) que se autenticou fornecendo os dados de registro solicitados. Normalmente, você cria contas de usuário para conceder acesso a partes exclusivas de seu site ou permitir que seus visitantes exibam seu conteúdo.

Para criar um novo usuário, você terá que seguir os seguintes passos:

'''1. Faça login no painel de administração do seu site web Joomla!'''

Abra uma nova janela do navegador e digite o URL correspondente. Isso seria algo como http://www.nome_do_seu_site_aqui.com/administrator
Assim que a página for carregada, inicie sessão como administrador do site. Atente-se que outras contas poderão não ter os direitos de adicionar novos usuários, dependendo do nível de acesso concedido. Mais sobre os níveis de acesso será mostrado mais adiante neste tutorial.

'''2. Abra o Gerenciador de Usuários'''

After logging in, go to the Site menu item, situated in the upper-left corner, right under the green bar separating the site header from the content area. In the opening menu select User Manager.

'''3. Add the new user'''

On the newly opened page, press the New button in the upper-right corner [[Image:Icon-32-new.gif]]. This will open the new user panel where you can enter the user data.
Now, let's fill in the user details:

'''Name''' - this field will contain the user's real name, like John Smith

'''Username''' - this would be the user or login name to be used to log in to the site, like jsmith or yellowbird67

'''New password''' - here you can enter a temporary password that you will send to the user so it can log in for the first time. The user will be able to change this later to something that is easy to remember. A good rule of thumb for choosing a safe password is to use small letters together with capitals and numbers while having a minimal length of six characters. A good example would be p9HWc0Ak.

'''Verify password''' - here you have to reenter the previously choosen password just to make sure there was no typo in the first one

'''Group''' - choosing the correct group to assign your user to may be crucial for your site's security so pay attention when setting this up! There is no golden-rule for choosing the user group except maybe for this one: "Keep the rights as low as posible". Normally, you wouldn't want to assign the Super Administrator or even Administrator role to just anyone. The Manager role is somewhat weaker but still strong enough to compromise your site's content. In 99% of the cases you will assign your users to the "Registered" group, thus only allowing them front-end access. In case you need more granularity of the access levels you might consider a third-party extension from the Extensions directory.

'''Block user''' - here you have the possibility to disable a previously created user account without deleting it. This option might be useful for banning users until they (or you) take a certain action. Simply set this option to Yes to disable the account.

'''Receive System E-mails''' - Set if the user should receive system relevant e-mails. If the user is an Administrator or Super Administrator you probably want to set this option to "No".

Next, set the parameters:

'''Back-end Language''' - this parameter sets the administration panel's language

'''Front-end Language''' - this parameter sets the website's panel's language when the user is logged in

'''User Editor''' - this parameter specifies which one of the built-in editors the user will be using while editing the information on the site

'''Help Site''' - here you can specify the location of the help files. These can be read from the files installed on your server (Local) or from the the Joomla! site (help.joomla.org). I usually prefer setting this option to help.joomla.org as this information tends to be more up to date.

'''Time Zone''' - well, this speaks for itself. Here you can set the user's time zone. This information will be used wherever time and date is displayed to the logged in user.

The Contact Information field will show the user's contact data if there is a corresponding entry in the Contact Manager.

Once you are done entering all the information above, click the Save button (the floppy disk icon in the upper-right corner).

If you have enabled the user (by setting the Block User field to No), it is now able to log in using the usename and login you have set.

'''Disabling/Banning a user'''

In order to disable or ban an existing user - not allowing them to login to the site - you will have to log in to the administration panel and open the User Manager from the Site menu -> User Manager. In the user list select the corresponding user by clicking on its name. In the newly opened panel, set the Block User option to Yes and press the Save button (the floppy disk icon in the upper-right corner).

Please note that this method will not delete the user account but will only disable it. You can always re-enable it by setting the Block User option to No.

'''Deleting a user'''

In order to delete a user from your database, log in to he administration panel as described above and choose Site -> User Manager from the top menu. On the opening page, select the checkbox to the left of the user's name you would like to remove and press the Delete button in the upper-right corner.

<noinclude>
[[Category:Tutorials/pt-br|Tutoriais]]
[[Category:User Management/pt-br|Gerenciador de Usuários]]
</noinclude>

Translations:Adding a new user/33/pt-br

2017-05-12T03:03:52Z

Juliano.freitas: Created page with "Tutoriais Gerenciador de Usuários"

[[Category:Tutorials/pt-br|Tutoriais]]
[[Category:User Management/pt-br|Gerenciador de Usuários]]

Adding a new user/pt-br

2017-05-12T03:03:29Z

Juliano.freitas: Created page with "'''2. Abra o Gerenciador de Usuários'''"

Translations:Adding a new user/7/pt-br

2017-05-12T03:03:28Z

Juliano.freitas: Created page with "'''2. Abra o Gerenciador de Usuários'''"

'''2. Abra o Gerenciador de Usuários'''

Adding a new user/pt-br

2017-05-12T03:03:14Z

Juliano.freitas: Created page with "Assim que a página for carregada, inicie sessão como administrador do site. Atente-se que outras contas poderão não ter os direitos de adicionar novos usuários, dependend..."

<noinclude><languages /></noinclude>
'''Adicionando um novo usuário'''

Um usuário é uma pessoa (ou grupo de pessoas) que se autenticou fornecendo os dados de registro solicitados. Normalmente, você cria contas de usuário para conceder acesso a partes exclusivas de seu site ou permitir que seus visitantes exibam seu conteúdo.

Para criar um novo usuário, você terá que seguir os seguintes passos:

'''1. Faça login no painel de administração do seu site web Joomla!'''

Abra uma nova janela do navegador e digite o URL correspondente. Isso seria algo como http://www.nome_do_seu_site_aqui.com/administrator
Assim que a página for carregada, inicie sessão como administrador do site. Atente-se que outras contas poderão não ter os direitos de adicionar novos usuários, dependendo do nível de acesso concedido. Mais sobre os níveis de acesso será mostrado mais adiante neste tutorial.

'''2. Open the User Manager'''

After logging in, go to the Site menu item, situated in the upper-left corner, right under the green bar separating the site header from the content area. In the opening menu select User Manager.

'''3. Add the new user'''

On the newly opened page, press the New button in the upper-right corner [[Image:Icon-32-new.gif]]. This will open the new user panel where you can enter the user data.
Now, let's fill in the user details:

'''Name''' - this field will contain the user's real name, like John Smith

'''Username''' - this would be the user or login name to be used to log in to the site, like jsmith or yellowbird67

'''New password''' - here you can enter a temporary password that you will send to the user so it can log in for the first time. The user will be able to change this later to something that is easy to remember. A good rule of thumb for choosing a safe password is to use small letters together with capitals and numbers while having a minimal length of six characters. A good example would be p9HWc0Ak.

'''Verify password''' - here you have to reenter the previously choosen password just to make sure there was no typo in the first one

'''Group''' - choosing the correct group to assign your user to may be crucial for your site's security so pay attention when setting this up! There is no golden-rule for choosing the user group except maybe for this one: "Keep the rights as low as posible". Normally, you wouldn't want to assign the Super Administrator or even Administrator role to just anyone. The Manager role is somewhat weaker but still strong enough to compromise your site's content. In 99% of the cases you will assign your users to the "Registered" group, thus only allowing them front-end access. In case you need more granularity of the access levels you might consider a third-party extension from the Extensions directory.

'''Block user''' - here you have the possibility to disable a previously created user account without deleting it. This option might be useful for banning users until they (or you) take a certain action. Simply set this option to Yes to disable the account.

'''Receive System E-mails''' - Set if the user should receive system relevant e-mails. If the user is an Administrator or Super Administrator you probably want to set this option to "No".

Next, set the parameters:

'''Back-end Language''' - this parameter sets the administration panel's language

'''Front-end Language''' - this parameter sets the website's panel's language when the user is logged in

'''User Editor''' - this parameter specifies which one of the built-in editors the user will be using while editing the information on the site

'''Help Site''' - here you can specify the location of the help files. These can be read from the files installed on your server (Local) or from the the Joomla! site (help.joomla.org). I usually prefer setting this option to help.joomla.org as this information tends to be more up to date.

'''Time Zone''' - well, this speaks for itself. Here you can set the user's time zone. This information will be used wherever time and date is displayed to the logged in user.

The Contact Information field will show the user's contact data if there is a corresponding entry in the Contact Manager.

Once you are done entering all the information above, click the Save button (the floppy disk icon in the upper-right corner).

If you have enabled the user (by setting the Block User field to No), it is now able to log in using the usename and login you have set.

'''Disabling/Banning a user'''

In order to disable or ban an existing user - not allowing them to login to the site - you will have to log in to the administration panel and open the User Manager from the Site menu -> User Manager. In the user list select the corresponding user by clicking on its name. In the newly opened panel, set the Block User option to Yes and press the Save button (the floppy disk icon in the upper-right corner).

Please note that this method will not delete the user account but will only disable it. You can always re-enable it by setting the Block User option to No.

'''Deleting a user'''

In order to delete a user from your database, log in to he administration panel as described above and choose Site -> User Manager from the top menu. On the opening page, select the checkbox to the left of the user's name you would like to remove and press the Delete button in the upper-right corner.

<noinclude>
[[Category:Tutorials]]
[[Category:User Management]]
</noinclude>

Translations:Adding a new user/6/pt-br

2017-05-12T03:03:14Z

Assim que a página for carregada, inicie sessão como administrador do site. Atente-se que outras contas poderão não ter os direitos de adicionar novos usuários, dependendo do nível de acesso concedido. Mais sobre os níveis de acesso será mostrado mais adiante neste tutorial.

Adding a new user/pt-br

2017-05-12T03:01:47Z

Juliano.freitas: Created page with "Abra uma nova janela do navegador e digite o URL correspondente. Isso seria algo como http://www.nome_do_seu_site_aqui.com/administrator"

<noinclude><languages /></noinclude>
'''Adicionando um novo usuário'''

Um usuário é uma pessoa (ou grupo de pessoas) que se autenticou fornecendo os dados de registro solicitados. Normalmente, você cria contas de usuário para conceder acesso a partes exclusivas de seu site ou permitir que seus visitantes exibam seu conteúdo.

Para criar um novo usuário, você terá que seguir os seguintes passos:

'''1. Faça login no painel de administração do seu site web Joomla!'''

Abra uma nova janela do navegador e digite o URL correspondente. Isso seria algo como http://www.nome_do_seu_site_aqui.com/administrator
Once the page is loaded, log yourself in as the site administrator. Please note that other accounts might not have the rights to add new users, depending on the granted access level. More about the access levels later in this tutorial.

'''2. Open the User Manager'''

After logging in, go to the Site menu item, situated in the upper-left corner, right under the green bar separating the site header from the content area. In the opening menu select User Manager.

'''3. Add the new user'''

On the newly opened page, press the New button in the upper-right corner [[Image:Icon-32-new.gif]]. This will open the new user panel where you can enter the user data.
Now, let's fill in the user details:

'''Name''' - this field will contain the user's real name, like John Smith

'''Username''' - this would be the user or login name to be used to log in to the site, like jsmith or yellowbird67

'''New password''' - here you can enter a temporary password that you will send to the user so it can log in for the first time. The user will be able to change this later to something that is easy to remember. A good rule of thumb for choosing a safe password is to use small letters together with capitals and numbers while having a minimal length of six characters. A good example would be p9HWc0Ak.

'''Verify password''' - here you have to reenter the previously choosen password just to make sure there was no typo in the first one

'''Group''' - choosing the correct group to assign your user to may be crucial for your site's security so pay attention when setting this up! There is no golden-rule for choosing the user group except maybe for this one: "Keep the rights as low as posible". Normally, you wouldn't want to assign the Super Administrator or even Administrator role to just anyone. The Manager role is somewhat weaker but still strong enough to compromise your site's content. In 99% of the cases you will assign your users to the "Registered" group, thus only allowing them front-end access. In case you need more granularity of the access levels you might consider a third-party extension from the Extensions directory.

'''Block user''' - here you have the possibility to disable a previously created user account without deleting it. This option might be useful for banning users until they (or you) take a certain action. Simply set this option to Yes to disable the account.

'''Receive System E-mails''' - Set if the user should receive system relevant e-mails. If the user is an Administrator or Super Administrator you probably want to set this option to "No".

Next, set the parameters:

'''Back-end Language''' - this parameter sets the administration panel's language

'''Front-end Language''' - this parameter sets the website's panel's language when the user is logged in

'''User Editor''' - this parameter specifies which one of the built-in editors the user will be using while editing the information on the site

'''Help Site''' - here you can specify the location of the help files. These can be read from the files installed on your server (Local) or from the the Joomla! site (help.joomla.org). I usually prefer setting this option to help.joomla.org as this information tends to be more up to date.

'''Time Zone''' - well, this speaks for itself. Here you can set the user's time zone. This information will be used wherever time and date is displayed to the logged in user.

The Contact Information field will show the user's contact data if there is a corresponding entry in the Contact Manager.

Once you are done entering all the information above, click the Save button (the floppy disk icon in the upper-right corner).

If you have enabled the user (by setting the Block User field to No), it is now able to log in using the usename and login you have set.

'''Disabling/Banning a user'''

In order to disable or ban an existing user - not allowing them to login to the site - you will have to log in to the administration panel and open the User Manager from the Site menu -> User Manager. In the user list select the corresponding user by clicking on its name. In the newly opened panel, set the Block User option to Yes and press the Save button (the floppy disk icon in the upper-right corner).

Please note that this method will not delete the user account but will only disable it. You can always re-enable it by setting the Block User option to No.

'''Deleting a user'''

In order to delete a user from your database, log in to he administration panel as described above and choose Site -> User Manager from the top menu. On the opening page, select the checkbox to the left of the user's name you would like to remove and press the Delete button in the upper-right corner.

<noinclude>
[[Category:Tutorials]]
[[Category:User Management]]
</noinclude>