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

change bug issue template to identify working branches of AU #190

Open
1 task done
ipajen opened this issue Nov 14, 2024 · 11 comments
Open
1 task done

change bug issue template to identify working branches of AU #190

ipajen opened this issue Nov 14, 2024 · 11 comments
Assignees
Labels
enhancement New feature or request needs triage needs to be discussed and worked on

Comments

@ipajen
Copy link
Collaborator

ipajen commented Nov 14, 2024

I have checked the following:

  • I've searched existing issues and found nothing related to my issue.

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

@ipajen ipajen added enhancement New feature or request needs triage needs to be discussed and worked on labels Nov 14, 2024
@asirota
Copy link
Member

asirota commented Nov 14, 2024

We need to eventually rename the branches. I want development nightly and stable.

@afragen
Copy link
Contributor

afragen commented Nov 14, 2024

I'm assuming we would also have feature branches as well.

@asirota asirota changed the title Imrpove Bug template of version Improve Bug template of version Nov 14, 2024
@asirota asirota self-assigned this Nov 14, 2024
@asirota
Copy link
Member

asirota commented Nov 14, 2024

Need some eyes on this @namithj @costdev --- what do you think about changing the branch names to be more respective of our core workflow:

  • main -> development
  • new branch called nightly which would be a pull from development into nightly every night at say 11pm Eastern Time (or some time we decide together)
  • playground-ready -> stable

This way PRs would go into development on a daily basis.

nightly would be a build someone could use to test the status of the current workflow.

stable would be the branch we cut into a release every time we complete a sprint/feature push.

Thoughts?

@ipajen
Copy link
Collaborator Author

ipajen commented Nov 15, 2024

Which of the branches could be open for merge, so @asirota don't need to accept all merges on each bransch.

@asirota
Copy link
Member

asirota commented Nov 15, 2024

We only do PR on main here. I also sometimes fix issue templates off the issue template branc

@asirota
Copy link
Member

asirota commented Nov 15, 2024

And of course translations.

@afragen
Copy link
Contributor

afragen commented Nov 15, 2024

translations is just a feature branch and should be removed once the feature is merged.

@afragen
Copy link
Contributor

afragen commented Nov 15, 2024

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.

@asirota
Copy link
Member

asirota commented Nov 16, 2024

Should we change the playgrounds blueprint to include test-reports plugin?

@asirota asirota changed the title Improve Bug template of version change bug issue template to identify working Nov 16, 2024
@asirota asirota changed the title change bug issue template to identify working change bug issue template to identify working branches of AU Nov 16, 2024
@ipajen
Copy link
Collaborator Author

ipajen commented Nov 16, 2024

Should we change the playgrounds blueprint to include test-reports plugin?

Yes would be great, also if there is a plugin to update wp-config.php would be great to include.

@afragen
Copy link
Contributor

afragen commented Nov 16, 2024

You can actually use the WP Debugging plugin to add things to wp-config.php via a filter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs triage needs to be discussed and worked on
Projects
None yet
Development

No branches or pull requests

3 participants