momocow / asuha Goto Github PK

The changes field in the payload of a push event is documented as follows.

An array with all the references that the push updated
(Source)

Currently the changes is treated as an object and accessed with object path push.changes.commits (Take commits field for example).
It should be push.changes[0].commits to retrieve the first change and so on.

Have asked on Atlassian forum to check if multiple changes should be handled.

A fix will be made if the meaning of changes field is clear.

Valid IP addresses for bitbucket.org has been updated. 😁

https://confluence.atlassian.com/bitbucket/what-are-the-bitbucket-cloud-ip-addresses-i-should-use-to-configure-my-corporate-firewall-343343385.html

Currently, repository scanning only uses the first remote tag in .git/config as the only one valid remote.

TODO

• Support multi-remote repositories

HTTP status 200 represents that the repository exists locally.
Otherwise 404 is returned to indicate that the git event from a remote repository hosted on an online host does not have a corresponding repository at local.

Instead of parsing .git/config, try to call git ls-remote via simple-git