Skip to content

added note about new --force option when running winter:up #239

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

Open
wants to merge 2 commits into
base: 1.3
Choose a base branch
from

Conversation

IsaiahPaget
Copy link

Relating to wintercms/winter#1363 (comment)

I am not exactly excited about how there are two point in this 'NOTE:'

Happy to change it if there is a better way to display this info!

@LukeTowers
Copy link
Member

We'll need to create a 1.3 branch for the docs and adjust the notes to reflect the config value that will be required to enable this behaviour that is being discussed in wintercms/winter#1363 (comment)

@IsaiahPaget
Copy link
Author

We'll need to create a 1.3 branch for the docs and adjust the notes to reflect the config value that will be required to enable this behaviour that is being discussed in wintercms/winter#1363 (comment)

Hey, so when it comes to making new branches, are you going to make a 1.3 branch and then merge this PR into it, or is that something I should do?

@LukeTowers LukeTowers changed the base branch from develop to 1.3 June 12, 2025 22:49
@LukeTowers
Copy link
Member

@IsaiahPaget I've created the branch and changed the target of this PR, thanks for the ping :)

@IsaiahPaget
Copy link
Author

Is there a local lint check I can do for these docs, so I can know they are passing before I push my commit?

@LukeTowers
Copy link
Member

We're using https://github.com/avto-dev/markdown-lint so I imagine you could just use the package that it uses.

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