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

Updated yard to 0.9.36 #102

Merged
merged 1 commit into from
Mar 8, 2024
Merged

Updated yard to 0.9.36 #102

merged 1 commit into from
Mar 8, 2024

Conversation

evolve75
Copy link
Owner

@evolve75 evolve75 commented Mar 8, 2024

This is a fix for a moderate CVE.

This is an integration commit for the virtual branches that GitButler is tracking.

Due to GitButler managing multiple virtual branches, you cannot switch back and
forth between git branches and virtual branches easily. 

If you switch to another branch, GitButler will need to be reinitialized.
If you commit on this branch, GitButler will throw it away.

Here are the branches that are currently applied:
 - Virtual branch (refs/gitbutler/Virtual-branch)
   branch head: 8d7d2c1e2b6e5d073c2e9eab95af2b7ce027a6f0
   - Gemfile.lock
   - rubytree.gemspec

Your previous branch was: refs/heads/master

The sha for that commit was: c9653ba

For more information about what we're doing here, check out our docs:
https://docs.gitbutler.com/features/virtual-branches/integration-branch
@evolve75 evolve75 merged commit aaf2b97 into master Mar 8, 2024
18 checks passed
@evolve75 evolve75 deleted the gitbutler/integration branch March 8, 2024 15:12
@coveralls
Copy link

Coverage Status

coverage: 94.416%. remained the same
when pulling ea52525 on gitbutler/integration
into c9653ba on master.

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.

3 participants