-
Notifications
You must be signed in to change notification settings - Fork 20
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
change bug issue template to identify working branches of AU #190
Comments
We need to eventually rename the branches. I want development nightly and stable. |
I'm assuming we would also have feature branches as well. |
Need some eyes on this @namithj @costdev --- what do you think about changing the branch names to be more respective of our core workflow:
This way PRs would go into
Thoughts? |
Which of the branches could be open for merge, so @asirota don't need to accept all merges on each bransch. |
We only do PR on main here. I also sometimes fix issue templates off the issue template branc |
And of course translations. |
|
FWIW, I know we're trying to copy the data from the Test Reports plugin. It's much simpler to copy that template in than to fill out all the information that is gathered automatically in the Test Reports plugin. |
Should we change the playgrounds blueprint to include test-reports plugin? |
Yes would be great, also if there is a plugin to update |
You can actually use the WP Debugging plugin to add things to |
I have checked the following:
Describe the feature you want to add
Version
What version of AspireUpdate are you running?
0.5 (default)
1.0
Nightly
What is nightly, it could be huge difference if its main, translate, playground-ready bransch.
Maybe add the fixed "main" , "playground-ready" and a new "other" for other like temp translation?
Mockups or Images of the feature
NA
The text was updated successfully, but these errors were encountered: