You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing out this tap, I noticed that, similarly to what happens in other variants of the tap-github out there, the Commits stream does not have the files and stats properties, as these ones can only be fetched commit by commit , but not when listing commits. These properties were once available in the Commits stream schema, but it became confusing for users that selected the stream to not see these data points materialised in their target (creating issues like this), hence they were removed by @dsprayberry in this PR.
In this same PR, the files and stats properties were also removed from the PrCommits stream (as they are also commit related streams). Although, unlike the Commits stream, these properties are available while listing commits for a PR, hence could be available in the PrCommits stream, even if they're not available in the Commits stream.
Functionally speaking, I'd also prefer that Github would keep their Commit related endpoints aligned and make files and stats available in both. Unfortunately this is not the case, but I still see the analytical value of having these fields available, even if only for commits that are linked to a Pull Request.
The text was updated successfully, but these errors were encountered:
While testing out this tap, I noticed that, similarly to what happens in other variants of the
tap-github
out there, theCommits
stream does not have thefiles
andstats
properties, as these ones can only be fetched commit by commit , but not when listing commits. These properties were once available in theCommits
stream schema, but it became confusing for users that selected the stream to not see these data points materialised in their target (creating issues like this), hence they were removed by @dsprayberry in this PR.In this same PR, the
files
andstats
properties were also removed from thePrCommits
stream (as they are also commit related streams). Although, unlike theCommits
stream, these properties are available while listing commits for a PR, hence could be available in thePrCommits
stream, even if they're not available in theCommits
stream.Functionally speaking, I'd also prefer that Github would keep their
Commit
related endpoints aligned and makefiles
andstats
available in both. Unfortunately this is not the case, but I still see the analytical value of having these fields available, even if only for commits that are linked to a Pull Request.The text was updated successfully, but these errors were encountered: