> <@unixia:matrix.org> > > <@unixia:matrix.org> Yes and the commit messages. You do not have to make an explanation in just the MR, it should go in commit messages. That is the entire point of commit messages. If I have to check how you made the changes say 2 months later, I'll see the commit log and the MR. So your commit messages should be descriptive and not ambiguous one liners.
> 
> > okay i see this , but what can we do in commit messages more ? in debian packaging please say , like should i write why control file is used plus every characters ?
> 
> Explain what your commit is doing. I am new to packaging. Seeing your commits I should be able to follow what you did there. If you write "add a random file" then maybe explain what that file does and why are you adding it.

if i am going to write this then it will take whole noob guide to cover it , plus if someone is new to packaging these things are there in every packaging and one knows these things when they start