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

Setup Notes for Deployed Application #36

Closed
wants to merge 1 commit into from

Conversation

joannenolan-sky
Copy link
Contributor

Here are the detailed setup notes that I have created for my team including screenshots and examples

@nikku
Copy link
Owner

nikku commented Jul 15, 2019

Thanks for your PR.

I had an improved getting started in my backlog for quite a while and came up with something. If you put yourself in your co-workers shoes, is this something they could work with? Or should we merge additional bits from your tutorial / docs?

@joannenolan-sky joannenolan-sky mentioned this pull request Jul 17, 2019
@joannenolan-sky
Copy link
Contributor Author

joannenolan-sky commented Jul 18, 2019

I think it would be good to include the permissions section as this has caused us issues in the past.
Also maybe a section about re-copying the Webhook secret if you see the signature mismatch error.

Just remembered another thing: the columns In Progress, Needs Review, and Done cannot be renamed as they are hard-coded into the automatic dev flow. Also if there is no column with label: null all issues will be put into the first column regardless of label

@nikku
Copy link
Owner

nikku commented Jul 18, 2019

I think it would be good to include the permissions section as this has caused us issues in the past.
Also maybe a section about re-copying the Webhook secret if you see the signature mismatch error.

A TROUBLESHOOTING document could be a good place for these two issues.

Just remembered another thing: the columns In Progress, Needs Review, and Done cannot be renamed as they are hard-coded into the automatic dev flow. Also if there is no column with label: null all issues will be put into the first column regardless of label

This sounds like a good target for better validation (#39). I'll probably rather implement validation than putting that in to a distinct document.

@joannenolan-sky
Copy link
Contributor Author

yeah that sounds like a good plan.

Just another quick one for the validation. If you run npm run all locally, it will use your local wuffle-config.js and fails if it is not using the default columns

@nikku
Copy link
Owner

nikku commented Jul 26, 2019

Another one for a TROUBLESHOOTING document: #43

Users must configure the appropritate login callback url.

@nikku
Copy link
Owner

nikku commented Jul 29, 2019

Just another quick one for the validation. If you run npm run all locally, it will use your local wuffle-config.js and fails if it is not using the default columns

This is not the case anymore.

@nikku
Copy link
Owner

nikku commented Jul 29, 2019

I've created the TROUBLESHOOTING document I've talked about: https://github.com/nikku/wuffle/blob/master/docs/TROUBLESHOOTING.md

Along with the vastly improved startup validation this should give users enough hints to know where to continue.

@nikku nikku closed this Jul 29, 2019
@wuffle-test-app wuffle-test-app bot removed the backlog label Jul 29, 2019
@nikku
Copy link
Owner

nikku commented Jul 29, 2019

Note that your setup instructions are outdated: As of v0.16.0 specifying repositories is no longer necessary, you control repository apperance on the board entirely via GitHub app installation.

@joannenolan-sky joannenolan-sky mentioned this pull request Jul 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants