roykoand opened a new issue, #69496:
URL: https://github.com/apache/airflow/issues/69496
### Under which category would you file this issue?
Airflow Core
### Apache Airflow version
3.2.2
### What happened and how to reproduce it?
Well, this is more of a nitpick and not that important, but there are quite
a few inconsistencies in Alembic migration descriptions that I noticed.
1) Some migration descriptions start from a capital letter, some from lower
case letter
| Revision | Description |
|----------|-------------|
| `53ff648b8a26` | `Add revoked_token table.` ✓ |
| `e79fc784f145` | `add timetable_type to dag table for filtering.` ✗ |
2) Some migration descriptions use imperative mood (Add, Remove, Fix) while
a few deviate (Added/Adding):
| Revision | Description |
|----------|-------------|
| `c4602ba06b4b` | `Added DagPriorityParsingRequest table.` ✗ |
| `8e1c784a4fc7` | `Adding max_consecutive_failed_dag_runs column to
dag_model table.` ✗ |
### What you think should happen instead?
Proposed standard:
- Start with a capital letter
- Use imperative mood (Add, Remove, Fix, Rename, etc.)
This matches what the majority already follows and is consistent with Git
commit message conventions.
A note in the contributor guide or a simple lint check could prevent this
from drifting further.
### Operating System
_No response_
### Deployment
None
### Apache Airflow Provider(s)
_No response_
### Versions of Apache Airflow Providers
_No response_
### Official Helm Chart version
Not Applicable
### Kubernetes Version
_No response_
### Helm Chart configuration
_No response_
### Docker Image customizations
_No response_
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
