-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Setup auto-publishing for Safari version #3686
Comments
@darthshadow has funded $10.00 to this issue.
|
@fregante has funded $10.00 to this issue.
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hey guys just finished reading the docs for fastlane and the great work over at lautis/refined-github-safari/fastlane So far I have 1 issue related to certificates - looking at docs.fastlane.tools/actions/match I believe sharing a provisioning profile would reduce the safari github action to: npm run build
bundle exec fastlane sign Due to limitations I understand the If While the above methods are friendly enough for non-apple developers to contribute on the extension, my main motivation is keeping the workflow logic (setting up ruby, node, auth and running commands) separated from fastlane and app store flows. If that sounds good I would be happy to move forward with a CI provisioning profile and automated github action builds for a pre-production environment - this can be used as an artifact to solve spam lagging app store releases or just compare with live version. TL;DR: Apple release process can be hacked quickly but I am not experienced enough in solving the credentials issue :D Happy to know your thoughts ! |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I prefer the CI machine approach. I would like the simplest setup possible. |
An anonymous user has funded $20.00 to this issue.
|
This comment has been minimized.
This comment has been minimized.
To get Fastlane configured, we will need to provide Apple ID developer credentials. Is it safe to assume that the project maintainer (@sindresorhus), or a collaborator @sindresorhus trusts and specifically delegates to should handle this? |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I see that this test build 21.3.5 requires macOS 10.15 or higher. It would be good if Safari 14 on macOS 10.14.6 could be supported, as previously mentioned: #3686 (comment) Thank you |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@fregante has funded $40.01 to this issue.
|
@sindresorhus has funded $100.00 to this issue.
|
Outdated intro
Refined GitHub is now also compatible with Safari (#3677), but it's not available on the App Store nor it's signed.
Safari users 👋
If you're looking to use Refined GitHub for Safari, for the time being it's best to use https://github.com/lautis/refined-github-safari
Xcode developers 👋
We need your help to:
How to build
Install XCode 12 and Safari 14
In Safari, enable Allow Unsigned Extensions in the Develop menu.
Run:
In Safari, click on the extension icon while on GitHub.com to enable it.
You could also sign it locally following the instructions below: #3686 (comment)
IssueHunt Summary
Backers (Total: $200.01)
Become a backer now!
Or submit a pull request to get the deposits!
Tips
The text was updated successfully, but these errors were encountered: