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

[CMS-1033] Use .gitattributes instead #106

Merged
merged 4 commits into from
Nov 28, 2022
Merged

[CMS-1033] Use .gitattributes instead #106

merged 4 commits into from
Nov 28, 2022

Conversation

jspellman814
Copy link

No description provided.

John Spellman added 2 commits November 22, 2022 10:24
* Add codeowners file

* Update version to 0.3.2

* Add GH action for wp.org release, .distignore file

* Add npm run readme command

* add CONTRIBUTING.md

* add badge back to readme.md

* try to Fix apt-get update

* use correct key

* Ignore contributing.md

* Update CONTRIBUTING.md with new workflow

* Update .distignore

* Remove changelog updates from this branch
jazzsequence
jazzsequence previously approved these changes Nov 28, 2022
Copy link
Contributor

@jazzsequence jazzsequence left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this should be sufficient.

Based on the comments in this PR for a similar deploy workflow and this WordPress StackExchange answer about what the .distignore is used by/for, I don't think we actually need it.

@jspellman814 jspellman814 merged commit 44e5fed into develop Nov 28, 2022
@jspellman814 jspellman814 deleted the cms-1033-v2 branch November 28, 2022 19:54
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