This template is designed to help you quickly start a new project with predefined issues and a GitHub project board.
💡 Recommendation: Read this entire guide carefully before executing the steps to ensure a smooth setup process.
Click on the "Use this template" button on the GitHub template repository page to create your new repository.
-
Navigate to Githubs Token Settings: Create Access Token
-
Personal access token: Click on "Generate new token (classic)".
-
Token settings: Give your token a descriptive name, set the expiration as desired, and select the
reposcope. This allows the token to access repositories. -
Generate token: Click "Generate token" at the bottom.
Important: Copy your new personal access token. You won’t be able to see it again!
💡 You can recreate your token at any time, so do not worry if you accidentally did not copy it
-
Clone your repository: Use
git cloneto clone your new repository to your local machine. -
Create
.envfile:-
Navigate to the root directory of your cloned repository.
-
Use the command line to create a copy of the
.env.examplefile:cp .env.example .env
-
Open the newly created
.envfile. -
Fill in your GitHub username, repository name, and the personal access token you created:
GITHUB_TOKEN=your_personal_access_token_here REPO_OWNER=your_github_username REPO_NAME=your_repository_name
-
-
- Check
.gitignore: Ensure that your.envfile is listed in your.gitignorefile to prevent it from being committed to your GitHub repository.
- Check
🚨 If you accidentally pushed your access token to GitHub, make sure to regenerate or remove it as fast as possible! This potentially grants access to your GitHub account.
💡 What is a `.env` file?
In the .env file, you can define variables and their values, which the application will read at runtime. This approach helps keep sensitive information, such as API keys and database credentials, secure and separate from the application's source code.
We need this file for our access token to ensure that the token remains private and is not hard-coded into the source code, protecting it from being exposed publicly.
In the root directory of your repository, run the following command to install necessary dependencies and run the issue creation script:
npm install
npm run create-issues💡 This script will automatically create predefined issues in your repository.
🚨 Make sure to run npm run create-issues only once for your repository.
✅ After creating the issues, you can revoke the token you created if you do not want to let it expire.
- Go to your repository on GitHub.
- Click on "Projects": Find the "Projects" tab and click on it.
- Create a new project: Click "New project", choose the "Board" template and name your project.
- Ensure that the visibility of your board is set to 'public'.
- Add issues: Click on "Add item" in the "ToDo" column.
- Select issues: Click on the "+" and "Add item from repository".
- Select repository: Select your project.
- Add to project: Select all items and click "Add selected items".
- Go to Vercel: Visit Vercel and sign up or log in.
- Import your project: Click on "New Project" and select your GitHub repository.
To ensure smooth collaboration, you need to add your team members as collaborators to both the GitHub repository and project board. Follow the steps below:
- Navigate to your repository on GitHub.
- Click the "Settings" tab at the top of the repository page.
- In the sidebar, click "Collaborators and Teams" under the Access section.
- Click the "Add Collaborator" button.
- Enter the GitHub username or email of each team member.
- Select the appropriate permission level (Write access is recommended for collaboration).
- Click "Add" to invite your team members.
- Navigate to the Project Board linked to your repository.
- Click the "Menu" button in the upper-right corner to open the board settings if not already visible.
- Click "Settings" and then "Manage Access".
- Click "Add Collaborators" and search for your team members by their GitHub username.
- Assign them the necessary access level to collaborate on the board.
- Your team members will receive an email or GitHub notification to accept the invitation.
- Ensure all members accept their invitations before starting the project to avoid access issues.
Start the development server:
npm run dev