Re: [GSoC] current working status
От | Charles Cui |
---|---|
Тема | Re: [GSoC] current working status |
Дата | |
Msg-id | CA+SXE9uxNQKRvKyH+g894qE=NKDRPHSm6EhZn0OFtwQwj=6UMA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [GSoC] current working status (Aleksander Alekseeev <a.alekseev@postgrespro.ru>) |
Ответы |
Re: [GSoC] current working status
|
Список | pgsql-hackers |
good idea, will keep a feature branch, and set up ci.
On Thu, Jun 14, 2018, 8:03 AM Aleksander Alekseeev <a.alekseev@postgrespro.ru> wrote:
Hello Charles,
> I saw the list of errors you posted. That's because I have some new
> function implemented and pushed without testing(in order forget my
> change in local machine).
> So you are saying it is best to keep each commit workable. Right?
Ideally, yes. You can always create a separate branch to experiment with
new code and merge it to master branch when it becomes stable. This is
not a strict GSoC requirement or something like this, but a good
practice. If something goes wrong you can just delete an experimental
branch and go back to working master branch.
--
Best regards,
Aleksander Alekseev
В списке pgsql-hackers по дате отправления: