Conversation
|
I don't think the Adding all files to a commit is very bad practice, also only allowing pushes to I think something that searches for the registered remotes and find one that matches the URL of EPITECH's git server (write that as a constant at the top of file) would be way more useful, instead of only allowing the remote named Also please only push to the currently selected branch and not |
|
Thank you for your advice. I will try my best
2018-10-02 9:08 GMT+02:00, Tina <notifications@github.com>:
… I don't think the `blih push` feature is well designed
Adding all files to a commit is very bad practice, also pushing to
origin/master is very limiting, and there's nothing related to EPITECH in
those implementation.
I think something that searches for the registered remotes and find one that
matches the URL of EPITECH's git server (write that as a constant at the top
of file) would be way more useful, instead of only allowing the remote named
`origin`.
Also please only push to the currently selected branch and not `master`.
Even better implementation would be to use the behavior defined in
`gitconfig` for `push.default` (see
https://git-scm.com/docs/git-config#git-config-pushdefault for reference)
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#2 (comment)
--
*Cordialement**,*
* http://www.epitech.eu/ <http://www.epitech.eu/>*
*Amir SARSENOV *
Etudiant 1ère année
Epitech. L'ecole de l'innovation
et de l'expertise informatique
Tel.: 06 24 54 48 00 <+33624544800>
24, rue Pasteur, 94270
Le Kremlin-Bicêtre, France
|
|
I found that it is hard to use current source code, which is in After some time of discussing with other students of Epitech, whether is My intentions is not to offend you or your team. I just wanted to have some real practice. |
Dear Emmanuel Vadot,
I have sent you an email (elbarto@bocal.org). Could you read please?