Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Update release note" is contaminating the git history #498

Closed
8 tasks done
kingyue737 opened this issue Nov 14, 2022 · 1 comment
Closed
8 tasks done

"Update release note" is contaminating the git history #498

kingyue737 opened this issue Nov 14, 2022 · 1 comment
Labels
question Further information is requested

Comments

@kingyue737
Copy link

First Check

  • I added a very descriptive title to this issue.
  • I used the GitHub search to find a similar issue and didn't find it.
  • I searched the SQLModel documentation, with the integrated search.
  • I already searched in Google "How to X in SQLModel" and didn't find any information.
  • I already read and followed all the tutorial in the docs and didn't find an answer.
  • I already checked if it is not related to SQLModel but to Pydantic.
  • I already checked if it is not related to SQLModel but to SQLAlchemy.

Commit to Help

  • I commit to help with one of those options 👆

Example Code

# Ignore

Description

Release note should be updated once before release, not after each commit. For example, you can achieve this by https://github.com/frinyvonnick/gitmoji-changelog. Currently it's hard to watch the git history.

image

Operating System

Windows

Operating System Details

No response

SQLModel Version

Ignore

Python Version

Ignore

Additional Context

No response

@kingyue737 kingyue737 added the question Further information is requested label Nov 14, 2022
@tiangolo
Copy link
Owner

Sorry, but I can't go and set up more CI stuff for this, there's a lot of things that need more urgent attention.

Given that, I'll pass on this request, but thanks for the interest. ☕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants