-
Notifications
You must be signed in to change notification settings - Fork 63
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
WIP: Playwright with shared repo, compared with master #236
base: master
Are you sure you want to change the base?
Changes from all commits
c24bd0f
a3871d2
389c10f
e52d248
c0d4dc3
ef99bdd
cce3e55
ab195be
15ea6cb
54c3133
007367f
23c6e32
6646dd0
8d22541
8bc4127
98e0dc2
3a94bd3
63284a8
721a285
4be1742
0e9c707
858d67e
67351b4
f48fdb2
745a291
3ac3aec
a798f8d
ab0fcd9
ae3e6d2
f848c87
cf843ad
1a37d61
8a698e3
dd496af
e3fb677
284e154
e2460ce
a5094ae
c2239ad
3c24235
17bbf7e
7c41fa3
8562797
d0e4119
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,3 @@ | ||
[submodule "e2e/playwright/mattermost-plugin-e2e-test-utils"] | ||
path = e2e/playwright/mattermost-plugin-e2e-test-utils | ||
url = https://github.com/mattermosttest/mattermost-plugin-e2e-test-utils.git | ||
Comment on lines
+1
to
+3
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't love seeing a submodule getting used here. It adds a lot of complexity. Are there simpler approaches that you considered? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @hanzei Yes the other two options I've considered is referencing through npm, and just duplicating the code. I definitely don't want to go down the route of duplicating the code. Publishing to npm or referencing as a git-based node dependency is probably what we will end up doing. The submodule approach was the quickest way that required no hassling with npm. Even if I didn't end up running into an issue with npm, I didn't want that to get in the way when trying this out. A git-based npm dependency wouldn't be much different as far as "use this commit", but I agree the submodule is not as turnkey as referencing a git-based dependency
Comment on lines
+1
to
+3
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should the repo be under the Mattermost org? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @hanzei Yes this was just the easiest way for me to have it somewhere other than my personal account. Since it is specifically related to Mattermost, and I was directly referencing it in a Mattermost project as a dependency, I sided to put it there for now. It's mainly a proof of concept to test out sharing code, and figuring out exactly which code should be shared etc. |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,9 +1,9 @@ | ||
node_modules/ | ||
node_modules | ||
.eslintcache | ||
.auth-user.json | ||
.env | ||
/blob-report/ | ||
/playwright/.cache/ | ||
.env | ||
test-results | ||
screenshots | ||
playwright-report | ||
test-results | ||
.auth-user.json | ||
.eslintcache |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there something we can generalize from this file and move into https://github.com/mattermost/actions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I want to "get it right" first though. I don't think we should merge two PRs from two different repos before moving this to the actions repo