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

Deploy alpha (test fast-forward worklow) #3088

Closed
wants to merge 205 commits into from
Closed

Deploy alpha (test fast-forward worklow) #3088

wants to merge 205 commits into from

Conversation

usu
Copy link
Member

@usu usu commented Oct 15, 2022

No description provided.

renovate bot and others added 30 commits July 29, 2022 23:37
Else the resolver used is not the same in dev and prod build.

If you print the pdf when running the frontend in npm run dev,
it uses @intlify/core::resolveValue.
(https://github.com/intlify/vue-i18n-next/blob/bb2e1770a0344b7d6993e03759cf8ba96d7a6396/packages/core-base/src/resolver.ts#L322)
If you print the pdf when running the frontend in npm run preview,
it uses @intlify/core::resolveWithKeyValue, which only supports flattened messages
with the jsonpath as key.
(https://github.com/intlify/vue-i18n-next/blob/bb2e1770a0344b7d6993e03759cf8ba96d7a6396/packages/core-base/src/resolver.ts#L305)

Fortunately the resolveValue function is exported and we can set the messageResolver when creating the context.

resolveFunction should be registered as MessageResolver when core.esm-browser.js
is included, but this does not happen somehow.
(https://github.com/intlify/vue-i18n-next/blob/bb2e1770a0344b7d6993e03759cf8ba96d7a6396/packages/core/src/index.ts)
This happens in the worker thread and when rendering the pdf in the main thread.

closes #3068
Only fast-forward if the comment is exactly '/fast-forward'
github.event.issue.pull_request is an empty string if it's
a pull request.
@carlobeltrame carlobeltrame temporarily deployed to dev October 30, 2022 09:39 Inactive
@carlobeltrame carlobeltrame temporarily deployed to dev October 30, 2022 09:39 Destroyed
frontend: get environment.js with the commit hash in the url
@carlobeltrame carlobeltrame temporarily deployed to dev October 30, 2022 15:14 Inactive
@carlobeltrame carlobeltrame temporarily deployed to dev October 30, 2022 15:15 Destroyed
@carlobeltrame carlobeltrame temporarily deployed to dev November 1, 2022 04:07 Inactive
@carlobeltrame carlobeltrame temporarily deployed to dev November 1, 2022 04:07 Destroyed
BacLuc and others added 3 commits November 1, 2022 20:27
And check write access and PR status by ourselves, because
the fine grained access token has the permission to merge without the review or checks beeing complete.
@carlobeltrame
Copy link
Member

/fast-forward

@github-actions
Copy link

github-actions bot commented Nov 2, 2022

The PR mergeable_state needs to be clean, was: blocked

@carlobeltrame
Copy link
Member

/fast-forward

@github-actions
Copy link

github-actions bot commented Nov 2, 2022

The PR mergeable_state needs to be clean, was: blocked

@carlobeltrame
Copy link
Member

When I query the API myself using a new personal API token on my account, I get "mergeable_state": "unstable", which would be fine (we should actually allow that, because it indicates that only non-required status checks such as Coveralls failed). That also matches with what the GitHub UI displays to me.
I don't understand why this workflow says it's "blocked"...

@github-actions
Copy link

github-actions bot commented Nov 2, 2022

The PR mergeable_state needs to be clean, was: blocked

@usu
Copy link
Member Author

usu commented Nov 2, 2022

/fast-forward

@github-actions
Copy link

github-actions bot commented Nov 2, 2022

The PR mergeable_state needs to be clean, was: blocked

@usu usu closed this Nov 2, 2022
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.

5 participants