Skip to content

Instantly share code, notes, and snippets.


Luis Matos luismts

View GitHub Profile
luismts /
Last active Oct 10, 2021
Git Tips and Git Commit Best Practices

Git Commit Best Practices

Basic Rules

Commit Related Changes

A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.

Commit Often

Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.

View xamarin.forms-dependencyservice.cs
/// XF Project
namespace UsingDependencyService
public interface IToDo {
void ToDo (); //note that interface members are public by default
namespace UsingDependencyService.Service
View xamarin.forms-restful.cs
public class RestService : IRestService
HttpClient client;
public RestService ()
client = new HttpClient (); // Creating the HTTPClient Object
View xamarin.forms-4.0-CollectionView.xaml
<CollectionView ItemsSource="{Binding Blogs}">
<Grid Padding="10">
<RowDefinition Height="Auto" />
<RowDefinition Height="Auto" />
View xamarin.forms-4.0-Visual.xaml
<ContentPage ...
View xamarin.forms-4.0-Shell.xaml
<Shell xmlns=""
x:Class=" TailwindTraders.Shell"
<ShellItem Title="Home">
<local:HomePage />
View xamarin.forms-3.4.0-ImageButton.xaml
<ImageButton Aspect="AspectFill" BorderColor="Purple" BorderWidth="3"
Source="xamarin_logo.png" AutomationProperties.HelpText="Xamarin Logo" />
luismts /
Created Nov 15, 2018 — forked from Chaser324/
GitHub Standard Fork & Pull Request Workflow

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j