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

⬆️ Update submodule #263

Merged
merged 4 commits into from
Sep 27, 2024
Merged

⬆️ Update submodule #263

merged 4 commits into from
Sep 27, 2024

Conversation

kirkkwang
Copy link
Contributor

This commit will update the submodule to mainly bring in the ruby-saml patch.

This commit will update the submodule to mainly bring in the ruby-saml
patch.
Gemfile.lock Outdated
@@ -1242,7 +1242,7 @@ GEM
multipart-post
oauth2
ruby-progressbar (1.13.0)
ruby-saml (1.16.0)
ruby-saml (1.17.0)
Copy link
Contributor

Choose a reason for hiding this comment

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

Gemfile.lock shouldn't exist in the knapsack, according to Rob

Copy link
Contributor Author

Choose a reason for hiding this comment

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

alright sounds good i can delete the whole thing then

Gemfile.lock files should not exist for knapsack projects apparently so
I am removing this.
Not sure why this lint isn't passing now, but this should fix it.
When running tests locally, a Gemfile.lock will generate, but we don't
want to commit it so ignoring it gets it out of the way.
@aprilrieger
Copy link
Contributor

@kirkkwang can this be closed?

@kirkkwang
Copy link
Contributor Author

@kirkkwang can this be closed?

Not yet, I need an approval and it has to get merged.

@bkiahstroud bkiahstroud merged commit eb0a66b into main Sep 27, 2024
6 checks passed
@bkiahstroud bkiahstroud deleted the update-submodule-ruby-saml-patch branch September 27, 2024 18:21
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.

4 participants