| Commit message (Collapse) | Author | Age | Lines |
... | |
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This allows the Fast Forward bot and GitHub Actions scripts through the
webhook filter.
* Fast Forward bot should be allowed as otherwise any event created by
this bot (i.e. it's merges to main) are not reported into Discord as it
is considered a bot payload
* GitHub Actions are generally things we have created ourselves and are
not normally high noise, and as such are also worth reporting
|
| | |
|
| |
| |
| |
| | |
Co-authored-by: wookie184 <[email protected]>
|
| | |
|
| |
| |
| |
| | |
A separate paragraph was used in the HTML, but another <p> was not actually used.
|
| | |
|
| |
| |
| |
| | |
I fixed them in PRs that were merged after the JSON used for this conversion was generated.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- There might be missing HTML that was stripped by `markdownify`
- Slugs were converted from kebab-casing titles and editorizing to make
everything shorter (thanks to oil.nvim)
- I should've just used Python and arrow (for the dates), but before I
realized arrow existed Nushell had the best built-in support.
- Markdown is wrapped at 80
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- The timeline app is introduced, moved from the home app.
- Add a basic README.md to illustrate the overall code breakdown of the
app as it is in the current stage.
- Two entries are added for now.
- Add ability to link headers using the slug portion of the filename.
- The way markdown files are fetched is similar to that of the resources
app - using the AppConfig ready() function, all resources are ensured
to be only fetched once when the app is first laoded.
I debated whether to introduce the new functionality in the home app
instead, without creating a new app. Eventually I decided extracting it
to a standalone app now is better as it allows easier extension of
functionality in the future. The home app can remain as it is to only
server the `/` homepage.
The timeline CSS is kept the same, as with the structure of the timeline
HTML template.
Once the CSS rewrite PR is merged, it's relatively easy to fix conflicts
here (again, since timeline is now its own app, with the CSS file and
HTML template moved - extra advantage).
References to `home:timeline` are updated to use `timeline:index`
throughout the codebase, as far as my ripgrep search could go.
The format of the markdown + YAML entries are still up for debate, so
I've only added the first two entries for now. They can be completely
overwritten in the future once the formats are decided by using a script
to convert all the data from my JSON file into individual markdown
files:
http://0x0.st/Xr78.txt
This link should last for at least a few months. (Originally saved on
https://paste.pythondiscord.com/KPJA, but it expires on 12th April 2024.)
|
|
|
|
|
| |
Introduce a way to store alternate accounts on the user, and add the
`PATCH /bot/users/<id:str>/alts` endpoint, which allows updating the
user's alt accounts to the alt accounts in the request..
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |\ |
|
| | |\ |
|
| | | |
| | | |
| | | |
| | | | |
Prevent spurious test failures on Solaris systems.
|
| | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Before, we had an N+1 query, where each tag would be separately fetched
and updated. Instead, first delete any tags we no longer care about,
then perform an upsert of all fields except for `last_commit`, which we
want to keep from the existing tag.
This comes with one caveat: on the first update of the tags, the `tags`
list is no longer modified in-place, because mutation is bad, however,
the database state is updated accordingly.
|
| | | |
|
| | |
| | |
| | | |
Co-authored-by: jchristgit <[email protected]>
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/ |
|
|/
|
|
|
|
| |
Any RunPython operation that only migrated existing data (that is, did
not create data) can be safely elided by Django when we run
`squashmigrations`.
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
|
| |
Allow faster local tests by skipping the database re-setup. Only two
cases were dependent on hardcoded IDs and already existing data, they
have been adjusted appropriately.
|
|\
| |
| | |
Timeline CSS refactor
|
| |
| |
| |
| | |
Co-authored-by: wookie184 <[email protected]>
|
| | |
|