boilerplate implementation of SafariPublisher #82
Conversation
| "type": "number", | ||
| "description": "defaults to GITHUB_RUN_NUMBER" | ||
| }, | ||
| "appleId": { |
There was a problem hiding this comment.
Are all these emails required or they are optional, and if any of them exist, the internal use it? - Quite intriguing, might be a bit overwhelm to the dev that uses this? I wonder if some of these email are just duplicate of each other? (Tho I assume they need to be separated for fastlane?)
| "type": "string", | ||
| "description": "i.e. \"18742801\" for Apple IDs in multiple teams" | ||
| }, | ||
| "provisioningProfiles": { |
There was a problem hiding this comment.
Can this be constructed from the other piece of data? Or is the idea that user can either providing a provisionProfiles array VS providing the granular detail above as singular fields?
There was a problem hiding this comment.
Since it seems to me the data in this profile object is the same as the data gathered so far above?
| "type": "string", | ||
| "description": "for S3" | ||
| }, | ||
| "workspace": { |
There was a problem hiding this comment.
do we need this for bpp or mainly for bms to test with?
| @@ -20,5 +20,18 @@ | |||
| "packageId": "123", | |||
| "csrftoken": "abcd", | |||
| "sessionid": "abcd" | |||
| }, | |||
No description provided.