You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even as it currently stands, having a .workspace configuration file (driven by dotenv) would be very useful. Being workspace is something users will likely run repeatedly, having each of the flags defaults would allow the user to essentially just run and-cli workspace and use the flags as overrides.
Right now, to bridge the gap, users could put a package.json at the top of their workspace root folder, add and-cli and configure a "project" cli (ie. workspace-cli) as well as create some aliases to make re-running these easier.
Use case: Contributor
As a contributor, I want to automatically have forks created and cloned ongoing to keep my workspace up-to-date with the latest AndcultureCode landscape of projects.
# .workspace
FORK=true
Use case: Maintainer
As a maintainer, I want to sync active contributor forks regularly to test out changes and more easily read larger PRs.
If --usernames flag is set, only sync those provided. In other words, don't merge config and incoming. Or so is my opinion on how it should work.
Even as it currently stands, having a
.workspace
configuration file (driven bydotenv
) would be very useful. Being workspace is something users will likely run repeatedly, having each of the flags defaults would allow the user to essentially just runand-cli workspace
and use the flags as overrides.Right now, to bridge the gap, users could put a package.json at the top of their workspace root folder, add
and-cli
and configure a "project" cli (ie.workspace-cli
) as well as create some aliases to make re-running these easier.Use case: Contributor
As a contributor, I want to automatically have forks created and cloned ongoing to keep my workspace up-to-date with the latest AndcultureCode landscape of projects.
Use case: Maintainer
As a maintainer, I want to sync active contributor forks regularly to test out changes and more easily read larger PRs.
If
--usernames
flag is set, only sync those provided. In other words, don't merge config and incoming. Or so is my opinion on how it should work.The text was updated successfully, but these errors were encountered: