> For the complete documentation index, see [llms.txt](https://doc.sysdevmobile.com/kalipso/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sysdevmobile.com/kalipso/6.0/how-to-guides/page-2.md).

# How to use GIT with Github

commit

## Best Practices

* Commit frequently with small, focused changes rather than large, mixed changes
* Write meaningful commit messages that explain the "why" behind your changes
* Review your changes before committing to ensure you're not including unintended modifications
* Use "Commit & Push" regularly when working with a team to keep everyone synchronized

pull / push

## Workflow Example

A typical Git workflow in Kalipso:

1. **Pull** - Get the latest changes from the remote
2. Make changes to your project (add forms, modify controls, etc.)
3. **Commit** - Save your changes locally with a descriptive message
4. **Pull** again - Check for any new changes from teammates
5. Resolve conflicts if any
6. **Push** - Share your changes with the team

{% hint style="success" %}
For quick workflows, use **Commit & Push** from the [Commit](/kalipso/6.0/documentation/git/commit.md) window to combine steps 3 and 6.
{% endhint %}

## Troubleshooting

### Push Rejected

If your push is rejected, it usually means the remote has changes you don't have locally:

1. Pull the latest changes
2. Resolve any merge conflicts
3. Commit the merge result
4. Push again

### Authentication Failed

If authentication fails:

* Verify your username is correct
* For GitHub/GitLab with two-factor authentication, use a Personal Access Token instead of your password
* Check that you have permission to push to the repository