Project Board to handle across all GitHub repositories!
MIT License
A Project Board to handle across all GitHub repositories!
My-Board-For-Github(MYFG) can also treat non-own project's issue and pull request. MYFG just require GitHub's issue/pr url for handling in the project board.
example-owner/my-board-data
project.json
into data repository
inbox
and done
id is special meaningrepo
scopehttps://my-board-for-github.netlify.app/?owner=<owner>&repo=<repo>&branch=<branch>&token=<token>
Parameters:
owner
: owner name of data repository
example-owner
repo
: repo name of data repository
my-board-data
branch
: branch name of data repository
master"
token
: GitHub Access Token for MYFG
xxxx
token
into localStorage and remove token
parameter from URL after token is passed.project.json
formatData repository require a project.json
file under the root directory.
project.json
schema is defined in src/data/DataScheme.ts.
[
{
"id": "activity",
"title": "Activity",
"type": "query",
"query": "involves:azu"
},
{
"id": "inbox",
"title": "Inbox",
"items": [
{
"url": "https://github.com/facebook/react/issues/19670",
"type": "issue"
},
{
"url": "https://github.com/microsoft/TypeScript/issues/40124",
"type": "issue"
}
]
},
{
"id": "progressing",
"title": "Progressing",
"items": [
]
},
{
"id": "done",
"title": "Done",
"items": [
{
"url": "https://github.com/github/roadmap/issues/65",
"type": "issue"
},
{
"url": "https://github.com/github/opensource.guide/pull/1704",
"type": "pull_request"
}
]
}
]
Sadly, the example require your GitHub Access Token, because GraphQL API always require Access Token.
Currently, My-Board-For-Github(MYFG) does not provide adding method yet.
Instead of it, Use Greasemonkey script for MYFG.
It allows you to add issue and pull request to your project from GitHub directly.
For more details, see userscript/github.
git checkout -b my-new-feature
git commit -am 'Add some feature'
git push origin my-new-feature
MIT
This project was bootstrapped with Create React App.
In the project directory, you can run:
yarn start
Runs the app in the development mode. Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits. You will also see any lint errors in the console.
yarn test
Launches the test runner in the interactive watch mode. See the section about running tests for more information.
yarn build
Builds the app for production to the build
folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes. Your app is ready to be deployed!
See the section about deployment for more information.
yarn eject
Note: this is a one-way operation. Once you eject
, you cant go back!
If you arent satisfied with the build tool and configuration choices, you can eject
at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject
will still work, but they will point to the copied scripts so you can tweak them. At this point youre on your own.
You dont have to ever use eject
. The curated feature set is suitable for small and middle deployments, and you shouldnt feel obligated to use this feature. However we understand that this tool wouldnt be useful if you couldnt customize it when you are ready for it.
You can learn more in the Create React App documentation.
To learn React, check out the React documentation.