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 crates/ and tools/ directories #475

Merged
merged 4 commits into from
Apr 13, 2022
Merged

Add crates/ and tools/ directories #475

merged 4 commits into from
Apr 13, 2022

Conversation

hannobraun
Copy link
Owner

See commit messages for justification. The reason I'm doing this now, is that I'm working on adding a second tool crate, as part of #54.

What do you think, @hendrikmaus? Since this affects release-operator and possibly the further automation of the relase process, both topics you've worked on exclusively, I'd love to get your input.

@hendrikmaus
Copy link
Contributor

From here it looks all fine and the structure makes sense to me. You've changed the relevant spots where paths needed adjustment already 👍🏻

@hannobraun
Copy link
Owner Author

Thanks for the feedback! I'm currently figuring out what I need to change to make the "file not found" error go away, then this is ready for merging.

@hannobraun hannobraun enabled auto-merge April 13, 2022 14:14
This has a few advantages:
1. There's less visual noise in the top folder, making it easier to
   become familiar.
2. It becomes more obvious, which of the folders contain Fornjot crates,
   as opposed to other crates that are not relevant outside of this
   repository.
3. It opens the door for further automation of the release process, by
   providing an easy way to detect all crates that should be published.
This has the following advantages:
1. It provides some implicit documentation on what release-operator is,
   making it easier to see at first glance what's relevant only inside
   this repository, and what's relevant to users.
2. It provides a place for adding more tools later, without creating a
   mess in the repository root.
@hannobraun
Copy link
Owner Author

Okay, turns out I moved the configuration file to crates/ accidentally. It should have stayed where it was.

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.

2 participants