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

Add arcade new Improvements #156

Merged
merged 16 commits into from
Dec 3, 2024
Merged

Conversation

EricGustin
Copy link
Contributor

@EricGustin EricGustin commented Nov 15, 2024

PR Description

This PR is a part of the community contributed toolkits story.

  • arcade new now uses jinja templates
  • arcade new now creates a "cookiecutter" toolkit equipped with everything a community contributed toolkit needs to be easily tested, published to PyPi, etc. as its own Github repo
  • I created the following toolkit with arcade new:

@EricGustin EricGustin marked this pull request as ready for review November 15, 2024 00:46
@EricGustin EricGustin requested a review from a team November 15, 2024 00:54
Copy link
Contributor

@Spartee Spartee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overall really great. This allows anyone to really quickly make a great toolkit. I made an obsidian toolkit really quickly with this. https://github.com/Spartee/arcade-obsidian

couple bumps we need to think about but overall great stuff.

Copy link

codecov bot commented Nov 25, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

Copy link
Collaborator

@nbarbettini nbarbettini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ship it ⛴️

Added some non-blocking nits and comments.

"toolkit_description": toolkit_description,
"toolkit_author_name": toolkit_author_name,
"toolkit_author_email": toolkit_author_email,
"arcade_version": f"{ARCADE_VERSION.rsplit('.', 1)[0]}.*",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit, but we are not validating this anywhere and just trusting that it has a .

Comment on lines +5 to +44
## Creating your new toolkit repo

1. Run `arcade new` and answer all the questions
2. Navigate to your new toolkit directory:
```bash
cd {{ toolkit_name }}
```
3. Initialize git repository:
```bash
git init
```
4. Create a new repository in Github with the same name as your new toolkit
> Note: Don't create a README, LICENSE or .gitignore when creating the repository because `arcade new` has already created these files for you.
5. Add remote and push your code:
```bash
git remote add origin https://github.com/{{ toolkit_author_name }}/{{ toolkit_name }}.git
git branch -M main
git add .
git commit -m "Initial commit"
git push -u origin main
```

## Publishing to PyPi

### Generating a PyPi API Key

1. Log into your PyPi account
2. Navigate to your Account settings and add an API token
3. Copy the token
4. In your Github repository:
- Go to Settings > Secrets and variables > Actions
- Click "New repository secret"
- Name your secret `PYPI_TOKEN`
- Paste your API Token into the Secret field

### Creating a Release

1. Navigate to your Github repository and click on Releases
2. Create a new tag that corresponds to the version in your toolkit's `pyproject.toml` file
> Note: This will be 0.0.1 for your first release
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It almost feels like these instructions belong somewhere else. This part is not really a README for the toolkit, but rather for the one-time process of creating a toolkit.

@EricGustin EricGustin requested review from Spartee and removed request for Spartee December 3, 2024 01:40
@nbarbettini nbarbettini merged commit 8dbbe23 into main Dec 3, 2024
5 checks passed
@nbarbettini
Copy link
Collaborator

Confirmed that all of @Spartee's review notes were either addressed in this PR, or will be filed as follow-ups by @EricGustin

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

Successfully merging this pull request may close these issues.

3 participants