-
Notifications
You must be signed in to change notification settings - Fork 35
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
Add Makefile for release #96
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems helpful, but the team should consider standard tooling and patterns going forward. I'd like to get towards having common patterns on our repos, and I don't think we use make anywhere else currently.
from setuptools import setup, find_packages | ||
from setuptools import find_packages, setup | ||
|
||
from readthedocs_ext import __version__ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We're using bump version on the theme and I'd like to start using that on all of our projects. It's a solution that doesn't require importing or reading files to get the version number, and allows us to standardize on setup.cfg
as well.
clean: | ||
rm -rf dist/ | ||
|
||
.PHONY: release clean tag |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems like a good improvement. I would like to settle on more common tooling patterns across our repos going forward though. On the other repos we're using inv
for this, which I quite like. That could maybe be a next step though. I'm generally a fan of make
otherwise.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 on standardization. I see that release
depends on clean
- not sure if invoke supports that sort of dependency tracking though. Brett Cannon asked on Twitter the other day and after a few recommendations, he went for doit https://twitter.com/brettsky/status/1382122878225686529
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Aren't we already using invoke for this? All our .org release tooling is built on it, so we should definitely standardize on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@astrojuanlu yeah, doit
helps a lot with cached dependencies too. However, invoke
supports pre-tasks http://docs.pyinvoke.org/en/latest/getting-started.html?highlight=pre#declaring-pre-tasks
I'm also 👍🏼 to avoid makefile and use invoke
here.
No description provided.