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

Workspace configuration file #119

Open
wintondeshong opened this issue Oct 3, 2020 · 0 comments
Open

Workspace configuration file #119

wintondeshong opened this issue Oct 3, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@wintondeshong
Copy link
Contributor

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.

# .workspace

USERNAMES=brandongregoryscott,wintondeshong
@wintondeshong wintondeshong added the enhancement New feature or request label Oct 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant