[DISCUSS] Fill the commit message when merge pull request

[Yingchun Lai <la...@apache.org>]

Hi Pegasus developers

Pegasus uses GitHub to manage codebase, new patches are reviewed and
merged by Pull Request. Now, each commit has only a short subject but
a lack of commit message, it's not easy and convenient to know what
the commits do except to open a browser to read the pull request
details.

So I suggest
- developers write some meaningful description when submit pull requests
- maintainers fill some necessary messages when merge pull requests
according to the description above


Best regards,
Yingchun

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org

Re: [DISCUSS] Fill the commit message when merge pull request

[Yingchun Lai <la...@apache.org>]

There is no veto, let's do it like this from now on.

On Tue, Feb 28, 2023 at 10:57 AM Yingchun Lai <la...@apache.org> wrote:
>
> Hi Pegasus developers
>
> Pegasus uses GitHub to manage codebase, new patches are reviewed and
> merged by Pull Request. Now, each commit has only a short subject but
> a lack of commit message, it's not easy and convenient to know what
> the commits do except to open a browser to read the pull request
> details.
>
> So I suggest
> - developers write some meaningful description when submit pull requests
> - maintainers fill some necessary messages when merge pull requests
> according to the description above
>
>
> Best regards,
> Yingchun

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@pegasus.apache.org
For additional commands, e-mail: dev-help@pegasus.apache.org