Explore tweets tagged as #mergeRequests
#openukawards tonight means it's 100% necessary to make as many penguin puns and use as many Pingu gifs as humanly possible. @phil_t_weir
0
0
3
50 commits, déjà 15 branches et des noeuds partout. Le graphe histo ressemble à une gare de triage 🤪.1e astuce: Settings>General>MergeRequests>Fast Forward.2e: rebaser!.3e: supprimer les branches au merge.4e: Normaliser les messages de commit.Ça ira bien mieux 😇
🔴 Depuis le 12 mai, la publication du code source de l'application #StopCovid sur le GitLab Inria continue d'être complétée. Le récapitulatif des publications en cours et à venir en thread ⬇️
0
0
0
The audience at @JamesMcWS' and my #NIDays presentation on #OpenSource was quite impressed with the level of details that @github provides in its web interface for handling #MergeRequests. FYI: @gitlab does the same thing 👍💜
0
1
2
It's happening! Merge requests are now enabled on opted-in projects on @drupal_org #MergeRequests #GitLab #Drupal #OpenSource
4
35
74
I think my students hate me because I only accept their homeworks and projects via #MergeRequests to the class #git repository. I like the workflow there because:.- You can see who committed/pushed what when.- You review and send feedback in the MR and you have all the context.
4
0
7
Just wondering; who is rebasing instead of merging? #git #rebase #merging #pullrequests #mergerequests.
0
0
0
2 GitLab Pro tips: 1. See MR rate (number of Merge Requests per week and month) under Insights => Merge requests, add /-/insights/#/mergeRequests to your project URL. 2. Close issue 3 automatically when the code is merged by adding "Closes #3" in the Merge Request description.
1
3
29