home / github

Menu
  • GraphQL API

commits

Table actions
  • GraphQL API for commits

4 rows where "author_date" is on date 2021-06-26

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: raw_author, raw_committer, author, committer, committer_date (date)

author_date (date) 1 ✖

  • 2021-06-26 · 4 ✖
sha ▼ message author_date committer_date raw_author raw_committer repo author committer
05a312caf3debb51aa1069939923a49e21cd2bd1 Applied Black, refs #1368 2021-06-26T22:25:28Z 2021-06-26T22:25:28Z Simon Willison 13ae486343ea6454a93114c6f558ffea2f2c6874 Simon Willison 13ae486343ea6454a93114c6f558ffea2f2c6874 datasette 107914493 simonw 9599 simonw 9599
089278b8dbe0cb3d41f27666d97b0096b750fbe2 rST fix, refs #1384 2021-06-26T22:49:07Z 2021-06-26T22:49:07Z Simon Willison 13ae486343ea6454a93114c6f558ffea2f2c6874 Simon Willison 13ae486343ea6454a93114c6f558ffea2f2c6874 datasette 107914493 simonw 9599 simonw 9599
0d339a4897c808903e34fa6be228cdaaa5a29c55 Removed text about executing SQL, refs #1384 2021-06-26T23:04:39Z 2021-06-26T23:04:39Z Simon Willison 13ae486343ea6454a93114c6f558ffea2f2c6874 Simon Willison 13ae486343ea6454a93114c6f558ffea2f2c6874 datasette 107914493 simonw 9599 simonw 9599
baf986c871708c01ca183be760995cf306ba21bf New get_metadata() plugin hook for dynamic metadata The following hook is added: get_metadata( datasette=self, key=key, database=database, table=table, fallback=fallback ) This gets called when we're building our metdata for the rest of the system to use. We merge whatever the plugins return with any local metadata (from metadata.yml/yaml/json) allowing for a live-editable dynamic Datasette. As a security precation, local meta is *not* overwritable by plugin hooks. The workflow for transitioning to live-meta would be to load the plugin with the full metadata.yaml and save. Then remove the parts of the metadata that you want to be able to change from the file. * Avoid race condition: don't mutate databases list This avoids the nasty "RuntimeError: OrderedDict mutated during iteration" error that randomly happens when a plugin adds a new database to Datasette, using `add_database`. This change makes the add and remove database functions more expensive, but it prevents the random explosion race conditions that make for confusing user experience when importing live databases. Thanks, @brandonrobertz 2021-06-26T22:24:54Z 2021-06-26T22:24:54Z Brandon Roberts 121af5c26cc703f7b3d7219091a8e71dc39db899 GitHub cd792325681cbad9f663f2879d8b69f1edbb678f datasette 107914493 brandonrobertz 2670795 web-flow 19864447

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options:

CREATE TABLE [commits] (
   [sha] TEXT PRIMARY KEY,
   [message] TEXT,
   [author_date] TEXT,
   [committer_date] TEXT,
   [raw_author] TEXT REFERENCES [raw_authors]([id]),
   [raw_committer] TEXT REFERENCES [raw_authors]([id]),
   [repo] INTEGER REFERENCES [repos]([id]),
   [author] INTEGER REFERENCES [users]([id]),
   [committer] INTEGER REFERENCES [users]([id])
);
CREATE INDEX [idx_commits_committer]
                ON [commits] ([committer]);
CREATE INDEX [idx_commits_author]
                ON [commits] ([author]);
CREATE INDEX [idx_commits_repo]
                ON [commits] ([repo]);
CREATE INDEX [idx_commits_raw_committer]
                ON [commits] ([raw_committer]);
CREATE INDEX [idx_commits_raw_author]
                ON [commits] ([raw_author]);
Powered by Datasette · Queries took 53.35ms · About: simonw/datasette-graphql