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

Isolate perennial behaviors and entry points that operate on SHAs #402

Open
samreid opened this issue Oct 24, 2024 · 1 comment
Open

Isolate perennial behaviors and entry points that operate on SHAs #402

samreid opened this issue Oct 24, 2024 · 1 comment

Comments

@samreid
Copy link
Member

samreid commented Oct 24, 2024

The main distinguishing characteristic of perennial is that it can operate on SHAs of perennial-alias. It seems important to demarcate the subset of perennial functionality that is about SHA operations. Perhaps a dedicated directory in perennial. We should make an effort to minimize tasks that forward from chipper to perennial, limiting it to the ones that perform SHA operations. It has been very confusing lately to be working in perennial and perennial-alias and not knowing which in getting invoked when, and after pushing a change having to pull the opposite repo right away to keep in sync.

@zepumph zepumph transferred this issue from phetsims/chipper Nov 7, 2024
@zepumph
Copy link
Member

zepumph commented Nov 7, 2024

Investigation of this will start over in #401

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

No branches or pull requests

2 participants