Skip to content

Setting up dev branch to be the v4 branch #912

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

Closed
wants to merge 2 commits into from
Closed

Conversation

vrdmr
Copy link
Member

@vrdmr vrdmr commented Nov 11, 2021

Description

Migrating dev branch to work for v4 version of the Functions.


PR information

  • The title of the PR is clear and informative.
  • There are a small number of commits, each of which has an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
  • If applicable, the PR references the bug/issue that it fixes in the description.
  • New Unit tests were added for the changes made and CI is passing.

Quality of Code and Contribution Guidelines

@vrdmr vrdmr requested a review from gavin-aguiar as a code owner November 11, 2021 21:04
@vrdmr vrdmr marked this pull request as draft November 12, 2021 21:23
@vrdmr vrdmr force-pushed the vameru/v4-readiness branch from a69968a to 25866f7 Compare November 16, 2021 02:05
@vrdmr
Copy link
Member Author

vrdmr commented Nov 16, 2021

Closing in favor of #914

@vrdmr vrdmr closed this Nov 16, 2021
@vrdmr vrdmr deleted the vameru/v4-readiness branch February 20, 2022 06:55
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.

1 participant