Andi Hubel
Andi Hubel
My error was to assume that you can alias existing fields. e.g. I created an alias `publish` with allowed values `yes, no`. The solution was to rename the field in...
Run into the same issue...
(note to self) I simply used JSON.stringify() around the restult as a temporary workaround: ```javascript logging.log("INIT", JSON.stringify(operation)); logging.log("RESULT", JSON.stringify(result)); ```
@johnjohndoe Whats the current state of this issue?
Related issue: #21
You write "Duplicate of #XXX" and Github adds a new "Timeline item", c.f. https://help.github.com/articles/about-duplicate-issues-and-pull-requests/ . But it looks like this item is currently not exported through the API, see https://platform.github.community/t/schema-request-un-marked-as-duplicate-timeline-events/5099...
You would need an additonal `added_issue_to_project` action.
The problem is that the issue has already to be on the board, before the `added_label` action works for this issue. You can add an issue to an board e.g....
https://github.com/pat-s/sperrorest/projects/1 @pat-s Maybe remove the parameter for `new_issue`. We use following configuration in our organisation board inbox column, which works fine:
Yes, at least we are using the app for private repos at work.