# Proposal create project coding standard for tryton

**URL:** <https://discuss.tryton.org/t/proposal-create-project-coding-standard-for-tryton/2295>\
**Category:** Organisation\
**Tags:** project\
**Created:** [February 5, 2020, 4:36pm UTC](https://discuss.tryton.org/t/proposal-create-project-coding-standard-for-tryton/2295 "2020-02-05T16:36:32Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![ced](https://discuss-cdn.tryton.org/user_avatar/discuss.tryton.org/ced/32/1237_2.png) [@ced](https://discuss.tryton.org/u/ced)\
**Post date:** [February 10, 2022, 4:38pm UTC](https://discuss.tryton.org/t/proposal-create-project-coding-standard-for-tryton/2295/12 "2022-02-10T16:38:52Z")

</div>

> [@ced](#):
>
> But at the end I think this can be applied only if we have a way to ignore the commit from the blame command.

Indeed the `hg annotate` command has a `--skip (EXPERIMENTAL)` option.  
[Mozilla is using it](https://bugzilla.mozilla.org/show_bug.cgi?id=1508002) with a custom command line that get revision from a file.  
I found also [this interesting way](https://stackoverflow.com/questions/20287201/is-there-a-way-to-ignore-a-commit-in-hg-blame#comment105659562_55194672) using pattern matching in commit message. It is probably slower than having a file with revision.  
Any way we should probably see for the [Heptapod migration](https://discuss.tryton.org/t/migration-of-development-to-heptapod/4971/13) to see what can be supported.

---

_[View the full topic](https://discuss.tryton.org/t/proposal-create-project-coding-standard-for-tryton/2295)._