Add a custom rule to prevent colors from being hardcoded outside of theme (#288)
* Add a custom rule to prevent colors from being hardcoded in ESLint * Refactor colors * Create packages folder and fix colors * Remove external dependency for css alphabetical order linting * Fix install with yarn --------- Co-authored-by: Charles Bochet <charles@twenty.com>
This commit is contained in:
16
packages/twenty-cli/src/install/contribute/remote.ts
Normal file
16
packages/twenty-cli/src/install/contribute/remote.ts
Normal file
@ -0,0 +1,16 @@
|
||||
import prompts, { PromptObject } from 'prompts';
|
||||
import open from 'open';
|
||||
|
||||
export const contributeRemoteQuestions: PromptObject<string>[] = [
|
||||
{
|
||||
type: 'text',
|
||||
name: 'local_setup_type',
|
||||
message:
|
||||
"We'll be redirecting you to a dedicated Github Codespace. Press enter to continue.",
|
||||
},
|
||||
];
|
||||
|
||||
export const askContributeRemoteQuestions: () => Promise<void> = async () => {
|
||||
await prompts(contributeRemoteQuestions);
|
||||
await open('https://codespaces.new/twentyhq/twenty');
|
||||
};
|
||||
Reference in New Issue
Block a user