-
Notifications
You must be signed in to change notification settings - Fork 5
Docs fragmentation #8
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
Comments
Good question, let me check into this and I'll get back with you soon. |
Upon research and talking with my developer friend, I agree that a new docs branch is the best strategy. I have created it and merged all changes from master into it. You can pull it, commit your changes to the documentation files, then submit the PR to merge back into master. I recommend to not do a compile/build, that way it does not regenerate |
The only part that will be a bit cumbersome is that you'll have to make your change in |
I worked on the username: admin, password: admin. Do an Also cleaned up the home component to show JWT details, and made it the default component after logging in. |
Awesome! I'll check it out tomorrow and do the whole |
You're welcome. I've been thinking about it and I want to use a new branch strategy. I'll rename the So,
|
That sounds good, a lot like GitFlow. I work that way too at my company, so it'll be natural for me. |
Yes, exactly. Sweet, I'll do that now. |
I've been working on very small doc updates on branch/barebones, but some things I will want to merge to master. Obviously, making a PR merges the whole branch into master, which is not wanted anymore since I already removed KendoUI and CKEdit.
How do we go about this? A separate docs branch?
The text was updated successfully, but these errors were encountered: