#dev-log

1 messages ยท Page 56 of 1

regal archBOT
ebon magnetBOT
#

Build 20201012.8 succeeded

Requested by

GitHub

Duration

00:02:22

Build pipeline

Site

regal archBOT
regal archBOT
#
        font-size: 0.9em;

0.8 feels a touch too small, feeling like I'm straining to read it when viewing both on 1080p and 1440p displays.

It also wasn't suitable to simply use zoom, as the size disparity between the timeline card title/content makes it look comical on zooming, along with it then needing to be adjusted between other pages and this timeline, as the general body text in the rest of the site doesn't need to be zoomed.

ebon magnetBOT
#

Build 20201012.9 succeeded

Requested by

GitHub

Duration

00:02:34

Build pipeline

Site

regal archBOT
regal archBOT
#

I don't really want to remove the Welcome to Python Discord from our front page, I think it's a valuable component and I almost want it to be there permanently.

That said, I do think having some sort of temporary notice for 100K would be great. I also think we need to put the timeline somewhere else so that it has a more permanent home - not sure precisely where this would be. I suppose our only real options are on the dropdown or in the resources. Both are a bit weird to me.

regal archBOT
#
jb3
[python-discord/forms-frontend] New branch created: build/new\-process
regal archBOT
regal archBOT
#
jb3
[python-discord/forms-frontend] branch deleted: build/new\-process
#
jb3
[python-discord/forms-frontend] New branch created: sentry/remove\-tracing
#
jb3
[python-discord/forms-frontend] branch deleted: sentry/remove\-tracing
regal archBOT
#
jb3
[python-discord/forms-frontend] New branch created: tests/increase\-coverage
#
jb3
[python-discord/forms-frontend] branch deleted: tests/increase\-coverage
regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201012.2 succeeded

Requested by

GitHub

Duration

00:02:48

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
#
jb3
[python-discord/forms-frontend] New branch created: build/chunking
#
jb3
[python-discord/forms-frontend] branch deleted: build/chunking
north knotBOT
#

Postgres backup completed!

ebon magnetBOT
#

Build 20201013.1 succeeded

Requested by

GitHub

Duration

00:01:05

Build pipeline

Seasonal Bot

regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201013.2 succeeded

Requested by

GitHub

Duration

00:03:25

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
ebon magnetBOT
#

Build 20201013.1 succeeded

Requested by

GitHub

Duration

00:03:06

Build pipeline

Bot

regal archBOT
north knotBOT
oak estuaryBOT
ebon magnetBOT
#

Build 20201013.2 succeeded

Requested by

GitHub

Duration

00:04:58

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201013.3 succeeded

Requested by

GitHub

Duration

00:01:08

Build pipeline

Seasonal Bot

regal archBOT
#
[python-discord/bot] New branch created: kwzrd/verification\-kicked\-note
regal archBOT
regal archBOT
regal archBOT
#

We've now had the Verification task kicking dormant unverified users from the guild for some time, and @lemonsaurus has raised the issue of having no easy way to determine whether a specific user was previously kicked by the system, and how many times.

Solution

In order to amend this issue, we decided to post a note infraction to site on-kick. This will give mods the ability to see that a specific user was kicked in their infraction history:

![image](https://user-images.githubuser...

ebon magnetBOT
#

Build 20201013.3 succeeded

Requested by

GitHub

Duration

00:03:02

Build pipeline

Bot

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201013.4 succeeded

Requested by

GitHub

Duration

00:00:50

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201013.4 failed

Requested by

Joseph Banks

Duration

00:00:54

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201013.5 failed

Requested by

Joseph Banks

Duration

00:00:52

Build pipeline

Bot

regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201013.6 succeeded

Requested by

Joseph Banks

Duration

00:04:41

Build pipeline

Bot

oak estuaryBOT
regal archBOT
#

Related to #428

On Sun, Oct 11, 2020 at 3:44 PM Chris Gallardo notifications@github.com
wrote:

I guess we could check if the code returns 404 cat, and if it does, and
the code isn't 404 we send something saying the code doesn't exist and show
404 cat.

โ€”
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/python-discord/seasonalbot/issues/500#issuecomment-706758040,
or unsubscribe
<https:...

regal archBOT
regal archBOT
#

We can add a backslash (\) to the end of each new line in its docstring
to fix that.

On Tue, Oct 13, 2020 at 5:10 AM Murad Bashirov notifications@github.com
wrote:

The help command for eval contains newlines that they should not be
there. That's because there are \ns after some words in docstring
https://github.com/python-discord/bot/blob/master/bot/exts/utils/snekbox.py#L281-L285.
And I'm not sure how to fix that.

[image: image]
<https://user-images.githubusercontent.co...

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201014.1 failed

Requested by

GitHub

Duration

00:00:57

Build pipeline

Bot

ebon magnetBOT
#

Build 20201014.2 failed

Requested by

GitHub

Duration

00:00:54

Build pipeline

Bot

ebon magnetBOT
#

Build 20201014.3 failed

Requested by

GitHub

Duration

00:01:06

Build pipeline

Bot

ebon magnetBOT
#

Build 20201014.4 failed

Requested by

GitHub

Duration

00:00:52

Build pipeline

Bot

ebon magnetBOT
#

Build 20201014.5 succeeded

Requested by

GitHub

Duration

00:02:47

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201014.6 succeeded

Requested by

GitHub

Duration

00:02:37

Build pipeline

Bot

north knotBOT
#

Postgres backup completed!

regal archBOT
ebon magnetBOT
#

Build 20201014.7 failed

Requested by

GitHub

Duration

00:00:55

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201014.8 succeeded

Requested by

GitHub

Duration

00:03:32

Build pipeline

Bot

#

Build 20201014.9 succeeded

Requested by

GitHub

Duration

00:03:21

Build pipeline

Bot

regal archBOT
#

You have solved the newline issue, but there are unrelated commits. And what you were trying was actually wrong. This

async def top_command(self, ctx: Context, subreddit: "subreddit_name") -> None:

means that the subreddit argument is should by instance of str; however, it should be instance of Subreddit and the default value of it should be 'r/Python'. The Subreddit is a converter, and forces a string to begin with "r/" and checks if it's a valid subreddit.

regal archBOT
regal archBOT
regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201014.1 succeeded

Requested by

GitHub

Duration

00:01:15

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201014.10 succeeded

Requested by

GitHub

Duration

00:02:45

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201014.11 succeeded

Requested by

GitHub

Duration

00:03:00

Build pipeline

Bot

#

Build 20201014.2 succeeded

Requested by

GitHub

Duration

00:01:05

Build pipeline

Seasonal Bot

regal archBOT
ebon magnetBOT
#

Build 20201014.3 succeeded

Requested by

GitHub

Duration

00:00:59

Build pipeline

Seasonal Bot

regal archBOT
#

@Anubhav1603 read what I said in #500. It isn't just 418.

The .http_cat command is supposed to send the picture associated with the status code the user enters. To check if the user has entered a valid status code, it checks if it is in the HTTPStatus enum. The problem with this, is that three of the status codes, 103 EARLY_HINTS, 418 IM_A_TEAPOT and 425 TOO_EARLY, are new to python version 3.9, though they are in http.cat. We should fix it so that these codes can be used.

ebon magnetBOT
#

Build 20201014.4 succeeded

Requested by

GitHub

Duration

00:01:01

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201014.12 succeeded

Requested by

GitHub

Duration

00:02:58

Build pipeline

Bot

regal archBOT
#

The syntax is ambiguous because it has a mix of syntaxes. [...] means the argument is optional and is used often in command help/man pages, while subreddit=r/Python is Python syntax for a default named argument, which could also be interpreted to mean "you have to include subreddit= in the command".

I think it would be clearer to have the command look like !reddit daily [subreddit] and add a notice that says "If no subreddit is specified, r/Python is the default" or something similar.

#

Can't add it as a suggestion but I think this would also be nice to add, would like to hear other opinions; not sure how other editors handle it, but at least pycharm views it as code in the docstring with full inspections which is helpful

    >>> class SomeCog(Cog):
    ...    # To initialize a valid RedisCache, just add it as a class attribute
    ...    # here. Do not add it to the __init__ method or anywhere else, it MUST
    ...    # be a class attribute. Do not pass any param...
oak estuaryBOT
regal archBOT
regal archBOT
regal archBOT
#
[python-discord/bot] New branch created: mbaruh\-duckpond
ebon magnetBOT
#

Build 20201014.13 succeeded

Requested by

GitHub

Duration

00:02:41

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201014.14 failed

Requested by

GitHub

Duration

00:01:01

Build pipeline

Bot

regal archBOT
#

b1f2b40 Move code block formatting detection to a separ... - MarkKoz
652bc5a Code block: add helper function to check for he... - MarkKoz
8af7162 Code block: add helper function to check channe... - MarkKoz
3b967c5 Code block: add helper function to check if msg... - MarkKoz
76eff08 Code block: add helper function to check for ch... - MarkKoz

ebon magnetBOT
#

Build 20201014.15 succeeded

Requested by

GitHub

Duration

00:04:33

Build pipeline

Bot

north knotBOT
oak estuaryBOT
ebon magnetBOT
#

Build 20201014.5 succeeded

Requested by

GitHub

Duration

00:02:05

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201015.1 succeeded

Requested by

GitHub

Duration

00:04:16

Build pipeline

Bot

oak estuaryBOT
regal archBOT
ebon magnetBOT
#

Build 20201015.1 succeeded

Requested by

GitHub

Duration

00:00:58

Build pipeline

Seasonal Bot

#

Build 20201015.2 failed

Requested by

GitHub

Duration

00:00:48

Build pipeline

Bot

ebon magnetBOT
#

Build 20201015.3 failed

Requested by

GitHub

Duration

00:00:54

Build pipeline

Bot

regal archBOT
#

When the bot pins a message, a 'notification' like Python pinned a message to this channel. See all the pins..

In reference to this (review comment), this message was kept to 'advertise the feature', now that most people this exists now, I think it's necessary to remove that message. The main reason for me is that sometimes (or most of the times?) people send something like 'hello' to claim the channel, and t...

#

@adhikariprajitraj have you looked at the contributing guides? It tells you that you need pipenv (pip install pipenv) and when setting up your development environment you use pipenv run precommit to install the hook, or you can run it manually using pipenv run lint, or just flake8 (the check that failed for this PR) using pipenv run flake8

you can refer [here](https://pythondiscord.com/pages/contributing/installing-project-dependenc...

regal archBOT
regal archBOT
north knotBOT
#

Postgres backup completed!

regal archBOT
ebon magnetBOT
#

Build 20201015.4 failed

Requested by

GitHub

Duration

00:01:02

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201015.5 failed

Requested by

GitHub

Duration

00:00:57

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201015.2 succeeded

Requested by

GitHub

Duration

00:00:56

Build pipeline

Seasonal Bot

regal archBOT
#

Hello @adhikariprajitraj.
It seems like your git history is quite messed up. Maybe you ran an auto formatter on the whole code at some point?

Also, it seems like you're working on your master branch, you should always work in another branch to avoid situations like that.

I'm closing this PR for now, feel free to delete your fork, fork again, and send a new PR, and I'll happily review it. If you have any question about the code or git itself, feel free to ask us in #dev-contrib!

ebon magnetBOT
#

Build 20201015.3 succeeded

Requested by

GitHub

Duration

00:01:06

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
#

This check should be inside the previous else block as that is where you are validating the given name.
example:

    @commands.command(name="prideleader", aliases=['pl'])
    async def pride_leader(self, ctx: commands.Context, *, pride_leader_name: Optional[str]) -> None:
        """Provides info about pride leader by taking name as input or randomly without input."""
        if pride_leader_name is None:
            name_list = [name for name in self.pride]
            le...
regal archBOT
#

Why is this variable named a? And what is the purpose of this code? It looks like it just re-packages the info into another dict. Maybe you could just return a["info"]? I think it's difficult to justify this especially given that you're renaming some of the keys, which just creates indirection elsewhere in the code. It would make more sense if you re-packaged this into e.g. a namedtuple, so that other code can access the values as attributes and have more of a guarantee that they will exist.

#

The try block should only contain code that you're expecting to raise. The else clause is semantically more appropriate for "code that should run if no exception is thrown". Alternatively, the except clause can return and then you can end the try-except block.

In this case, I think the following would make the most sense:

try:
    info = get_info(...)
except error:
    embed = error_embed()
else:
    embed = success_embed(info)

send embed
#

At the moment, eval automatically truncates output that is greater than 10 lines, or has more than 1000 characters.

The eval formatter cuts off the output past 1000 characters with a "message is too long" message, and past 10 lines with a "too many lines" message. However, it also at the moment is set (with MAX_PASTE_LEN) to not upload results that have more than 1000 characters.

        elif len(output) >= 1000:
            truncated = True
            output = f"{output[:...
#

Description

We can perhaps make the .hackstats command only show valid repos instead of total contributions.

Reasoning

Many ppl use the discord bot to keep track of their repos and they will be in the delusion that some of their PRs were qualified, when they might have been invalid as the HacktoberFest team is closing submissions from certain large public repos, due to lack of quality.

Would you like to implement this yourself?

  • [ ] I'd like to implement this fe...
ebon magnetBOT
#

Build 20201015.7 succeeded

Requested by

GitHub

Duration

00:02:42

Build pipeline

Bot

regal archBOT
#

Maybe we can put a message in the availabe/dormat embed saying that the first message in this channel is pinned so others can jump back to the original question and discussions.

And in the case of when the user deletes their message after claiming the channel, maybe the bot can say something like This channel is claimed by @ user it will be moved to dormat after xyz minutes, it doesn't look like the bot moved the channel to occupied for no reason whatsoever.

north knotBOT
ebon magnetBOT
#

Build 20201015.4 succeeded

Requested by

GitHub

Duration

00:03:04

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

north knotBOT
ebon magnetBOT
#

Build 20201015.5 succeeded

Requested by

GitHub

Duration

00:03:12

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201015.6 failed

Requested by

GitHub

Duration

00:00:54

Build pipeline

Seasonal Bot

ebon magnetBOT
#

Build 20201015.6 failed

Requested by

GitHub

Duration

00:00:57

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201015.7 succeeded

Requested by

GitHub

Duration

00:03:08

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201015.8 succeeded

Requested by

GitHub

Duration

00:03:13

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201015.9 succeeded

Requested by

GitHub

Duration

00:03:10

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201015.8 succeeded

Requested by

GitHub

Duration

00:04:49

Build pipeline

Bot

oak estuaryBOT
ebon magnetBOT
#

Build 20201016.1 succeeded

Requested by

GitHub

Duration

00:01:04

Build pipeline

Seasonal Bot

regal archBOT
#

This mostly works, but sometimes there is a 400 error because the embed has a field with an empty value:

discord.errors.HTTPException: 400 Bad Request (error code: 50035): Invalid Form Body
In embed.fields.0.value: This field is required

I'm also concerned about the terms of service for the TMDB API, which states

You shall use the TMDb logo to identify your use of the TMDb APIs.

You shall place the following notice prominently on your application: "This product us...

ebon magnetBOT
#

Build 20201016.2 succeeded

Requested by

GitHub

Duration

00:00:57

Build pipeline

Seasonal Bot

regal archBOT
ebon magnetBOT
#

Build 20201016.3 succeeded

Requested by

GitHub

Duration

00:00:52

Build pipeline

Seasonal Bot

north knotBOT
#

Postgres backup completed!

ebon magnetBOT
#

Build 20201016.4 succeeded

Requested by

GitHub

Duration

00:01:09

Build pipeline

Seasonal Bot

ebon magnetBOT
#

Build 20201016.5 succeeded

Requested by

GitHub

Duration

00:01:15

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201016.6 succeeded

Requested by

GitHub

Duration

00:00:56

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
#

Description

TMDB API ToS states under section 3 (attribution):

You shall use the TMDb logo to identify your use of the TMDb APIs.
You shall place the following notice prominently on your application: "This product uses the TMDb API but is not endorsed or certified by TMDb."
Any use of the TMDb logo in your application shall be less prominent than the logo or mark that primarily describes the application and your use...

regal archBOT
ebon magnetBOT
#

Build 20201016.7 succeeded

Requested by

GitHub

Duration

00:00:59

Build pipeline

Seasonal Bot

regal archBOT
#
[python-discord/bot] New branch created: mbaruh\-inf\-id
north knotBOT
ebon magnetBOT
#

Build 20201016.8 succeeded

Requested by

GitHub

Duration

00:03:18

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
ebon magnetBOT
#

Build 20201016.1 succeeded

Requested by

GitHub

Duration

00:02:42

Build pipeline

Bot

regal archBOT
#
[python-discord/bot] New branch created: mbaruh\-user\-command
#

The stat code should be left untouched, but currently message sending is handled over 3 methods: in this one, in get_pep_embed and in validate_pep_number. From the two checking coros it's not immediately apparent that they will send message from their names and the sending doesn't need to be handled inside of them, as all their paths where the messages are sent are already being checked in here.

ebon magnetBOT
#

Build 20201016.2 succeeded

Requested by

GitHub

Duration

00:02:52

Build pipeline

Bot

regal archBOT
#
[python-discord/bot] branch deleted: kwzrd/verification\-kicked\-note
#

7b40cb6 Verification: implement kick note post helper - kwzrd
ba7429a Verification: add notes to kicked users - kwzrd
5f4552f Verification: simplify kick note reason - kwzrd
54fb163 Verification: avoid logging whole kick note pay... - kwzrd
5df2fa2 PR #1233 Verification: add note to kicked members - kwzrd

north knotBOT
ebon magnetBOT
#

Build 20201016.3 succeeded

Requested by

GitHub

Duration

00:04:52

Build pipeline

Bot

oak estuaryBOT
regal archBOT
#

A permanent infraction will have its "Remaining" attribute displayed as "Expired" due to the following lines of code:

https://github.com/python-discord/bot/blob/5df2fa2f948852826322409103c91565390110fe/bot/exts/moderation/infraction/management.py#L264

Remaining is "None" not because it has expired, but because there is no defined time remaining for an infraction that is not scheduled to expire. Previously, there was a suggestion in issue #668:

For fun, we could put (โˆž) next to perm...

regal archBOT
north knotBOT
#

Postgres backup completed!

regal archBOT
ebon magnetBOT
#

Build 20201017.1 succeeded

Requested by

GitHub

Duration

00:00:55

Build pipeline

Seasonal Bot

regal archBOT
#
[python-discord/site] branch deleted: feat/timeline
north knotBOT
regal archBOT
ebon magnetBOT
#

Build 20201017.1 succeeded

Requested by

Leon Sandรธy

Duration

00:04:19

Build pipeline

Site

regal archBOT
#
[python-discord/bot] New branch created: sebastiaan/features/whitelister\-sprinters
#

To make sure we're not interrupting the Core Devs when they're having their Core Dev Sprint, I've added the Sprinters role to our constants and added them to our filter whitelist. To make this easier, I've now made it so all filter features that use a role whitelist use the same role whitelist constant. That makes maintenance a bit easier.

In the process, I've also added a few line breaks in config-default.yml to kaizen it up: Now all groups have two line breaks between them.

ebon magnetBOT
#

Build 20201017.1 succeeded

Requested by

GitHub

Duration

00:03:07

Build pipeline

Bot

regal archBOT
#
[python-discord/bot] branch deleted: sebastiaan/features/whitelister\-sprinters
#

57786e9 Restrict nsfw subreddit(s) or similar (subreddi... - RohanJnr
0b836a5 Merge remote-tracking branch 'upstream/master' ... - RohanJnr
f32a665 Filter out reddit posts which are meant for use... - RohanJnr
d8fbeed handling empty list error in get_top_posts() me... - RohanJnr
3554a57 re-add comment. - RohanJnr

north knotBOT
ebon magnetBOT
#

Build 20201017.2 succeeded

Requested by

GitHub

Duration

00:04:31

Build pipeline

Bot

oak estuaryBOT
regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201017.3 succeeded

Requested by

GitHub

Duration

00:04:25

Build pipeline

Bot

oak estuaryBOT
regal archBOT
ebon magnetBOT
#

Build 20201017.2 succeeded

Requested by

GitHub

Duration

00:00:57

Build pipeline

Seasonal Bot

regal archBOT
#
[python-discord/bot] New branch created: mbaruh\-mod\-channels
regal archBOT
ebon magnetBOT
#

Build 20201017.4 succeeded

Requested by

GitHub

Duration

00:02:50

Build pipeline

Bot

regal archBOT
#
[python-discord/bot] branch deleted: mbaruh\-inf\-id
north knotBOT
ebon magnetBOT
#

Build 20201017.5 succeeded

Requested by

GitHub

Duration

00:04:43

Build pipeline

Bot

regal archBOT
regal archBOT
regal archBOT
regal archBOT
regal archBOT
#

The purpose of this PR is to provide one location in the code which is responsible for checking whether a given channel is a mod channel.

Currently this check is performed in the following locations:

  • !user - If it's a mod channel, it will also display notes and nominations.
  • The moderation management cog - only works in mod channels.
  • When issuing infractions - mod channels will display infraction number, and total number of infractions for the user.

Issues begin when the defin...

ebon magnetBOT
#

Build 20201017.6 succeeded

Requested by

GitHub

Duration

00:02:38

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201017.7 failed

Requested by

GitHub

Duration

00:00:53

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201017.8 succeeded

Requested by

GitHub

Duration

00:02:49

Build pipeline

Bot

regal archBOT
#

Prevailing style for a multi-line expression would be:

return (
    a
    or b
)

How would you feel about handling each case separately and logging the decision made? For example:

def is_mod_channel(channel: discord.TextChannel) -> bool:
    """True if `channel` is considered a mod channel."""
    if channel.id in constants.MODERATION_CHANNELS:
        log.trace(f"Channel #{channel} is a configured mod channel")
        return True

    mod_categories ...
north knotBOT
ebon magnetBOT
#

Build 20201017.9 succeeded

Requested by

GitHub

Duration

00:04:42

Build pipeline

Bot

oak estuaryBOT
regal archBOT
ebon magnetBOT
#

Build 20201017.10 failed

Requested by

GitHub

Duration

00:00:53

Build pipeline

Bot

regal archBOT
#

Hi, thanks for your contribution. We ask that new contributors only work on approved issues, to ensure that we are interested in the feature being developed. The code you have added does not solve any existing issues, imports dependencies that we do not use, and does not align with our contributing guidelines. For these reasons I am going to close this pull request. Please review the linked document and start with opening an...

regal archBOT
#

Thank you for contributing to Python Discord!

Please check out the following documents:

ebon magnetBOT
#

Build 20201017.2 succeeded

Requested by

GitHub

Duration

00:02:22

Build pipeline

Site

regal archBOT
#
[python-discord/bot] New branch created: feat/global\-bot
ebon magnetBOT
#

Build 20201017.11 succeeded

Requested by

GitHub

Duration

00:02:48

Build pipeline

Bot

regal archBOT
#

This could be just be and a consequence of this being new, but when going over it I thought of bot as a regular object that held the instance, which made it a bit confusing. I think something like the name bot_instance that's imported using a from import could be clearer.

Now there are two methods of accessing the bot: the global instance, and the argument that gets passed to all cogs. Should this be unified to use the global instance? It'd be more consistent within this codebase, but ...

ebon magnetBOT
#

Build 20201017.12 succeeded

Requested by

GitHub

Duration

00:02:40

Build pipeline

Bot

regal archBOT
#

Having to do from bot.bot import bot is a little eh,

In such case, the name could be bot_instance, which would ease confusion.

but I'd probably prefer it to what's happening in the init with this approach.

The redis session and intents code would have to be moved over too. I don't like the idea of substantial code execution upon import, even if that may be a more superficial contention in this case. __main__.py does slightly feel like a better place for this code, but a...

#

Thanks, I think it's better this way. Logging the exact decision helps a lot during testing. The caller can always log more context ~ both before, and after the check ~ if necessary.

The code is functional and I agree that this is an improvement. Please double-check the configured category IDs. I cannot help verify them as I don't see those channels.

It's good to include the phrase "Closes #1175" ([or a variation thereof](https://docs.github.com/en/enterprise/2.16/user/github/managing-y...

regal archBOT
#

In such case, the name could be bot_instance, which would ease confusion.

I'd prefer that name a lot.

I don't like the idea of substantial code execution upon import, even if that may be a more superficial contention in this case.

I think it's fine given the context of our project. It's code that has to execute at init time either way, before the bot connects. The difference is just the module in which it happens. However now that I think about it, moving it to bot.bot would ca...

regal archBOT
regal archBOT
#
jb3

Okay, all tested locally and everything works. However, some notes.

  • Putting feedback in the channel does not work. We should just be DMing the user about this and telling them in the channel to check their DMs, it's way better UX and means you don't have to read super fast in 10s and then have it get deleted.
  • We should be using embeds like we do elsewhere on the bot, either a nice green for voice gate succeed and red for failure.
regal archBOT
ebon magnetBOT
#

Build 20201018.1 failed

Requested by

GitHub

Duration

00:01:03

Build pipeline

Bot

regal archBOT
#

I've decided to do some refactoring with __init__.py and __main__.py before trying out moving the instance variable to bot.py. But then I realised I somewhat strongly prefer the explicitness of assigning the instance to the variable in __main__.py rather than having it be done implicitly upon importing bot.py. This left the following arguments:

  1. The circular import circumvention for the type annotation is ugly
    • Sure, but I don't think it's so bad; I don't mind. I think it...
ebon magnetBOT
#

Build 20201018.2 succeeded

Requested by

GitHub

Duration

00:02:38

Build pipeline

Bot

ebon magnetBOT
#

Build 20201018.1 succeeded

Requested by

GitHub

Duration

00:00:56

Build pipeline

Seasonal Bot

north knotBOT
#

Postgres backup completed!

ebon magnetBOT
#

Build 20201018.3 succeeded

Requested by

GitHub

Duration

00:02:49

Build pipeline

Bot

ebon magnetBOT
#

Build 20201018.8 failed

Requested by

GitHub

Duration

00:02:34

Build pipeline

Bot

#

Build 20201018.9 failed

Requested by

GitHub

Duration

00:02:12

Build pipeline

Bot

#

Build 20201018.10 failed

Requested by

GitHub

Duration

00:02:26

Build pipeline

Bot

ebon magnetBOT
#

Build 20201018.11 succeeded

Requested by

GitHub

Duration

00:02:52

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201018.13 failed

Requested by

GitHub

Duration

00:00:49

Build pipeline

Bot

#

Build 20201018.14 failed

Requested by

GitHub

Duration

00:00:51

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201018.15 failed

Requested by

GitHub

Duration

00:02:37

Build pipeline

Bot

#

Build 20201018.16 succeeded

Requested by

GitHub

Duration

00:02:50

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201018.22 succeeded

Requested by

GitHub

Duration

00:03:09

Build pipeline

Bot

regal archBOT
#

9035611 Create base Voice Gate cog - ks129
7039702 Define Voice Gate channel, role and requirement... - ks129
80409d4 Add voice gate configuration to config-default.yml - ks129
0d05c45 Merge remote-tracking branch 'up/master' into v... - ks129
9c1f66e Add voice ban icons and show appeal footer for ... - ks129

north knotBOT
ebon magnetBOT
#

Build 20201018.23 succeeded

Requested by

GitHub

Duration

00:04:56

Build pipeline

Bot

oak estuaryBOT
regal archBOT
#

This PR makes two adjustments to the voice gating system:

In-Channel response fallback.
At the moment, the bot will attempt to DM the verification result for a member which is reliant on privacy settings allowing member DMs. This commit should add a suitable fallback of sending the response in the voice-verification channel instead. As the channel will delete all bot messages automatically after 10 seconds, there was no need to add a delete_after argument to the message sent in-channe...

ebon magnetBOT
#

Build 20201018.24 succeeded

Requested by

GitHub

Duration

00:02:56

Build pipeline

Bot

regal archBOT
#
jb3
[python-discord/bot] branch deleted: voice\-gate\-dm\-failed
north knotBOT
ebon magnetBOT
#

Build 20201018.25 succeeded

Requested by

Joseph Banks

Duration

00:04:49

Build pipeline

Bot

oak estuaryBOT
regal archBOT
#
[python-discord/seasonalbot] New branch created: roll\-prefix\-msg
#

Description

The command previously sent ! as the prefix, while . is the correct one. Now imports prefix from bot.constants, so it'll always be up to date.

Screenshots

Previous output:

New output:

Did you:

  • [x] Join the Python Discord Community?
  • [x] If dependencies have been added or updated, run pipenv lock?
  • [x] Lint your code (pipenv run lint)?
  • [x] Set the PR to allow edits from contributors?
ebon magnetBOT
#

Build 20201018.2 succeeded

Requested by

GitHub

Duration

00:00:59

Build pipeline

Seasonal Bot

regal archBOT
#
[python-discord/seasonalbot] branch deleted: roll\-prefix\-msg
north knotBOT
ebon magnetBOT
#

Build 20201018.3 succeeded

Requested by

GitHub

Duration

00:03:01

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
#
[python-discord/bot] New branch created: voice\-gate\-delay\-grant
#

When verified users get their role, they cannot see the voice-verification channel anymore, so I've added a 3 second delay for granting the role in order to ensure there's some time for them to see the response.

I've also moved the DM message to only be sent if the DM message succeeds, and to not mention them in-channel to avoid distracting them from the DM notification unnecessarily, as I'm sure they'll see a near-instant response to their command usage in that channel.

ebon magnetBOT
#

Build 20201018.26 failed

Requested by

GitHub

Duration

00:00:48

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201018.27 succeeded

Requested by

GitHub

Duration

00:03:11

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201018.28 succeeded

Requested by

GitHub

Duration

00:02:50

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201018.29 succeeded

Requested by

GitHub

Duration

00:03:05

Build pipeline

Bot

regal archBOT
north knotBOT
#
Auto-deployed: metricity
north knotBOT
#
Auto-deployed: metricity
ebon magnetBOT
#

Build 20201018.1 failed

Requested by

Joseph Banks

Duration

00:01:29

Build pipeline

Site

north knotBOT
regal archBOT
ebon magnetBOT
#

Build 20201018.2 succeeded

Requested by

Joseph Banks

Duration

00:04:09

Build pipeline

Site

north knotBOT
regal archBOT
ebon magnetBOT
#

Build 20201018.3 succeeded

Requested by

Joseph Banks

Duration

00:04:39

Build pipeline

Site

regal archBOT
#
[python-discord/bot] branch deleted: mbaruh\-duckpond
#
[python-discord/bot] branch deleted: mbaruh\-user\-command
#

Currently, if two users invoke the silence command at the same time, the value of the second silence will go to the redis cache while the first value will be used in the scheduler, causing some very weird behaviour, apart from the unexpected two silences going through.
We should use a lock on the command for the channel it was invoked in. There shouldn't be any issues from multiple unsilences as far as I can see but also using a lock there doesn't seem like a bad idea

#

async-rediscache does quite a few debug logs per operation, which drown out the bot logs around them without bringing information of much relevance when developing on the bot, pushing the logging level to only show warnings should keep the logs from the module only to what may matter.

Currently the module only does a couple of error logs and one critical log in places where an exception is raised anyway, but this will make sure that warnings still go through in case they are added in the f...

ebon magnetBOT
#

Build 20201018.30 succeeded

Requested by

GitHub

Duration

00:02:50

Build pipeline

Bot

regal archBOT
#

I'm not sure this is necessary. It would make sense for a system with mainly experienced users, but we have a constant stream of new users using the system, so there is never really a point at which we don't need to advertise it anymore.

It might be worth it to reduce noise in the help channel, but it doesn't cause much of it, and it would have to be worth potentially hiding this feature from a lot of users.

regal archBOT
#

Not sure if this is doable without a whitelist of some kind; without keeping some kind of whitelist/blacklist for urls we could keep a list of extensions we don't want through (commonly malicious stuff like rar, exe, etc.) and if the url path ends with one of them, block the message. This shouldn't interfere with paste services since they'll end with extensions that won't be there, but some sites may use the "extension" for something else.

#
jb3

5cc01bc Ensure verified users can see verified message. - scragly
7b8f857 Address a grammar error in failed reasons. - scragly
0bf48fc Instruct to reconnect to voice channel if conne... - scragly
f0ba0c2 Merge pull request #1247 from python-discord/vo... - jb3

#
jb3
[python-discord/bot] branch deleted: voice\-gate\-delay\-grant
north knotBOT
ebon magnetBOT
#

Build 20201019.1 succeeded

Requested by

Joseph Banks

Duration

00:04:50

Build pipeline

Bot

oak estuaryBOT
regal archBOT
#

I quite like the idea. Like Mark said as well, having it only sends DMs of possible would be a nice addition. The only real issue I can see with that is the user not realising that the message was deleted and sending it again. Maybe we could reduce the server message to something simple that mentions the main cause of the deletion and asks the user to check their DMs for more info. If they donโ€™t have DMs enabled, it would simply be like today.

regal archBOT
north knotBOT
#

Postgres backup completed!

regal archBOT
regal archBOT
#
[python-discord/bot] branch deleted: mbaruh\-mod\-channels
north knotBOT
ebon magnetBOT
#

Build 20201019.2 succeeded

Requested by

GitHub

Duration

00:05:18

Build pipeline

Bot

oak estuaryBOT
regal archBOT
regal archBOT
#
[python-discord/site] New branch created: allow\-internal\-dns\-api
#

Currently, we're experiencing some issues requesting API data via the public domain, likely caused by some Cloudflare weirdness.

This change puts the internal domain api.site, referenceable through the internal Docker DNS only, in the whitelist of ALLOWED_HOSTS.

This should be merged before making further changes, so we can confirm the internal domain works as expected after a deployment and before we move change the bot to use it.

ebon magnetBOT
#

Build 20201019.1 succeeded

Requested by

GitHub

Duration

00:02:29

Build pipeline

Site

regal archBOT
#
[python-discord/bot] New branch created: internal\-dns\-api
#

Currently, we're experiencing some issues requesting API data via the public domain, likely caused by some Cloudflare weirdness.

This change sets the internal domain api.site, referenceable through the internal Docker DNS only, as the default API domain in config.

This should be not merged until https://github.com/python-discord/site/pull/413 and https://github.com/python-discord/salt/pull/21 are both merged and tested manually to resolve correctly.

ebon magnetBOT
#

Build 20201019.3 succeeded

Requested by

GitHub

Duration

00:03:14

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201019.4 succeeded

Requested by

GitHub

Duration

00:02:56

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201019.5 succeeded

Requested by

GitHub

Duration

00:03:06

Build pipeline

Bot

regal archBOT
#
            prev_record = self.candy_records.get(str(user.id), 0)
            self.candy_records[str(user.id)] = prev_record + 1

This previously added the candies to the person who sent the message and not to the person who clicked the candy. user.id will get the ID of the person who reacted to the message, while message.author.id will get the ID of the person who sent the message. An easy fix once you spot the issue.

north knotBOT
#

Postgres backup completed!

regal archBOT
regal archBOT
regal archBOT
regal archBOT
regal archBOT
#
[python-discord/bot] New branch created: mbaruh\-user\-command
regal archBOT
#

Ah, I didn't realise that these would only work on the top hash and not its keys where we actually store the data.
You mentioned some kind of rewrite on discord, what would that involve? Currently not having access to things like idletime and key expires limits the usability of the package as a more complex cache (setting on every get is a bit redundant when redis has the functionality in an another type), is this out of scope for now or would the rewrite allow it?

#
[python-discord/bot] New branch created: feat/help/refactor
regal archBOT
ebon magnetBOT
#

Build 20201020.1 succeeded

Requested by

GitHub

Duration

00:02:59

Build pipeline

Bot

regal archBOT
north knotBOT
#

Postgres backup completed!

ebon magnetBOT
#

Build 20201021.1 succeeded

Requested by

GitHub

Duration

00:01:01

Build pipeline

Seasonal Bot

ebon magnetBOT
#

Build 20201021.2 failed

Requested by

GitHub

Duration

00:00:00

Build pipeline

Seasonal Bot

regal archBOT
ebon magnetBOT
#

Build 8674 failed

Requested by

GitHub

Duration

00:00:00

Build pipeline

Seasonal Bot

north knotBOT
ebon magnetBOT
#

Build 20201021.3 succeeded

Requested by

Sebastiaan Zeeff

Duration

00:03:25

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
ebon magnetBOT
#

Build 20201021.4 succeeded

Requested by

GitHub

Duration

00:00:58

Build pipeline

Seasonal Bot

north knotBOT
ebon magnetBOT
#

Build 20201021.5 succeeded

Requested by

GitHub

Duration

00:03:04

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201021.1 succeeded

Requested by

Joseph Banks

Duration

00:04:29

Build pipeline

Bot

oak estuaryBOT
regal archBOT
ebon magnetBOT
#

Build 20201021.6 succeeded

Requested by

GitHub

Duration

00:00:59

Build pipeline

Seasonal Bot

#

Build 20201021.7 succeeded

Requested by

GitHub

Duration

00:01:02

Build pipeline

Seasonal Bot

regal archBOT
ebon magnetBOT
#

Build 20201021.8 failed

Requested by

GitHub

Duration

00:00:59

Build pipeline

Seasonal Bot

ebon magnetBOT
#

Build 20201021.9 succeeded

Requested by

GitHub

Duration

00:01:02

Build pipeline

Seasonal Bot

ebon magnetBOT
#

Build 20201021.1 succeeded

Requested by

GitHub

Duration

00:02:38

Build pipeline

Site

regal archBOT
ebon magnetBOT
#

Build 20201021.2 succeeded

Requested by

GitHub

Duration

00:02:28

Build pipeline

Bot

north knotBOT
ebon magnetBOT
#

Build 20201021.3 succeeded

Requested by

GitHub

Duration

00:04:40

Build pipeline

Bot

oak estuaryBOT
regal archBOT
#

Relevant Issues

Closes #277

Description

We have added a file called spooknamerate.py which contains relevant code for the game.

Everyday, a random name is generated from a list of first and last names. (The data was downloaded from mockaroo). This name is sent in #seasonalbot-commands and the users need to spookify the name and register it using the command .spooknamerate add the name.

Two hours before the game ends, a poll is sent out, a...

ebon magnetBOT
#

Build 20201021.10 failed

Requested by

GitHub

Duration

00:00:56

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201021.2 succeeded

Requested by

GitHub

Duration

00:02:18

Build pipeline

Site

regal archBOT
north knotBOT
regal archBOT
ebon magnetBOT
#

Build 20201021.3 succeeded

Requested by

Joseph Banks

Duration

00:04:01

Build pipeline

Site

regal archBOT
ebon magnetBOT
#

Build 20201021.4 failed

Requested by

Joseph Banks

Duration

00:01:29

Build pipeline

Site

#

Build 20201021.4 succeeded

Requested by

GitHub

Duration

00:02:25

Build pipeline

Bot

north knotBOT
regal archBOT
ebon magnetBOT
#

Build 20201021.5 succeeded

Requested by

Joseph Banks

Duration

00:04:00

Build pipeline

Site

regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201022.1 succeeded

Requested by

Joseph Banks

Duration

00:04:07

Build pipeline

Site

#

Build 20201022.1 succeeded

Requested by

GitHub

Duration

00:03:24

Build pipeline

Bot

north knotBOT
regal archBOT
ebon magnetBOT
#

Build 20201022.2 succeeded

Requested by

Joseph Banks

Duration

00:04:30

Build pipeline

Site

regal archBOT
#

I propose these changes to the mute command:

  • Allow muting off-server users. Sometimes we will apply a mute a moment after a user leaves the server, causing it to fail. This leads us to look for some other measure, such as banning them for the same duration. There shouldn't be a technical problem to apply a mute to someone outside the server, since it's already applied on join. At the same time we can add info about the user not being on the server for infractions applied in mod channels....
regal archBOT
#
[python-discord/site] New branch created: frontpage\-100k
#

This is a draft PR to track the progress of the first stage of the frontpage design update.

The following things are being aimed for:

  • [ ] Slight structure change to add wave hero section.
  • [ ] Add in some form of promotional banner/image/section for the 100K member milestone.
  • [ ] Add in some form of clear frontpage link to the new timeline page.
  • [ ] Lazy load the embedded video to provide a cleaner thumbnail design by default.

The following is part of the TODO list for this P...

ebon magnetBOT
#

Build 20201022.3 succeeded

Requested by

GitHub

Duration

00:02:33

Build pipeline

Site

regal archBOT
ebon magnetBOT
#

Build 20201022.4 succeeded

Requested by

GitHub

Duration

00:02:28

Build pipeline

Site

regal archBOT
ebon magnetBOT
#

Build 20201022.5 succeeded

Requested by

GitHub

Duration

00:02:20

Build pipeline

Site

regal archBOT
ebon magnetBOT
#

Build 20201022.6 succeeded

Requested by

GitHub

Duration

00:02:25

Build pipeline

Site

regal archBOT
ebon magnetBOT
#

Build 20201022.7 succeeded

Requested by

GitHub

Duration

00:02:56

Build pipeline

Site

north knotBOT
#

Postgres backup completed!

regal archBOT
#

Can't fully review it at the moment, but most of the things I found now are done multiple places in the code. One comment counts for all the instances.

I'm also not a fan of all the # comments around the code, most of them don't add any value, just noise. For instance
if final: # if it is the final
The code here is self explanatory, and dont need the comment.
While this is a good comment, since I was about to question why you're sleeping there for 1 sec.
`await asyncio.sleep(1) ...

#

I like this quite a bit. It looks good, the code is great, overall a solid PR.

I have only two pieces of feedback, but they're not showstoppers.

  1. I think we should get rid of the Discord cutout element in the top right now that we have this design. We'd probably be better off just having the More dropdown in the top right and adding the Discord link as a normal navbar item alongside Reddit and so on.

  2. This PR has a slightly lower comment-to-code ratio than would be ideal. Which i...

#

Description

currently, if a github username is not found, it sends No valid october contributions found for username, which is a bit misleading. Now it sends Github user not found: username.

Reasoning

(For get_october_prs)

  1. When user not found, it returns None
  2. Error, returns None
  3. No october PRs, return empty list
  4. No valid hacktoberfest PRs, return empty list

This way, get_stats can handle the cases and send user-not-found or no-prs messages accordingl...

ebon magnetBOT
#

Build 20201022.2 succeeded

Requested by

GitHub

Duration

00:01:00

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201022.8 succeeded

Requested by

GitHub

Duration

00:02:19

Build pipeline

Site

regal archBOT
regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201022.3 succeeded

Requested by

GitHub

Duration

00:03:10

Build pipeline

Seasonal Bot

night lilyBOT
#
SeasonalBot

Connected!

north knotBOT
regal archBOT
ebon magnetBOT
#

Build 20201022.9 succeeded

Requested by

GitHub

Duration

00:04:21

Build pipeline

Site

regal archBOT
#
[python-discord/bot] New branch created: Hemlock/Add\_eval\_to\_voice\_chats
north knotBOT
ebon magnetBOT
#

Build 20201022.2 succeeded

Requested by

GitHub

Duration

00:05:02

Build pipeline

Bot

oak estuaryBOT
regal archBOT
ebon magnetBOT
#

Build 20201022.3 failed

Requested by

GitHub

Duration

00:02:29

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201022.4 succeeded

Requested by

GitHub

Duration

00:03:09

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201022.5 succeeded

Requested by

GitHub

Duration

00:02:56

Build pipeline

Bot

regal archBOT
ebon magnetBOT
#

Build 20201022.6 succeeded

Requested by

GitHub

Duration

00:02:59

Build pipeline

Bot

regal archBOT
#
[python-discord/bot] branch deleted: Hemlock/Add\_eval\_to\_voice\_chats
north knotBOT
ebon magnetBOT
#

Build 20201022.7 succeeded

Requested by

GitHub

Duration

00:05:09

Build pipeline

Bot

oak estuaryBOT
ebon magnetBOT
#

Build 20201022.4 failed

Requested by

GitHub

Duration

00:01:05

Build pipeline

Seasonal Bot

regal archBOT
#
[python-discord/bot] branch deleted: mbaruh\-user\-command
north knotBOT
oak estuaryBOT
ebon magnetBOT
#

Build 20201022.8 succeeded

Requested by

GitHub

Duration

00:05:01

Build pipeline

Bot

ebon magnetBOT
#

Build 20201022.5 failed

Requested by

GitHub

Duration

00:00:48

Build pipeline

Seasonal Bot

north knotBOT
ebon magnetBOT
#

Build 20201022.9 succeeded

Requested by

GitHub

Duration

00:04:40

Build pipeline

Bot

oak estuaryBOT
ebon magnetBOT
#

Build 20201022.7 failed

Requested by

GitHub

Duration

00:01:02

Build pipeline

Seasonal Bot

ebon magnetBOT
#

Build 20201022.8 failed

Requested by

GitHub

Duration

00:00:57

Build pipeline

Seasonal Bot

north knotBOT
#

Postgres backup completed!

regal archBOT
#

Description

  • Updated PRs 'created' time range to the range @mattipv4 told me
  • updated categorising prs logic, now PRs that are after the review period but created before october 3rd will count

Reasoning

for some people the PRs listed wasn't the same as the ones on the website, those PRs are the ones from before october 3rd, and passed review period. Now it's listed

Screenshots

Before/after
![345B6A06-7130-4372-A7FA-22D4A6053B76](https://user-images.githubusercont...

ebon magnetBOT
#

Build 20201023.1 succeeded

Requested by

GitHub

Duration

00:00:59

Build pipeline

Seasonal Bot

regal archBOT
#
[python-discord/bot] New branch created: mbaruh/menu
ebon magnetBOT
#

Build 20201023.2 failed

Requested by

GitHub

Duration

00:00:59

Build pipeline

Seasonal Bot

regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201023.1 succeeded

Requested by

GitHub

Duration

00:02:27

Build pipeline

Site

regal archBOT
#

The PR has been updated taking into account you've made here @lemonsaurus as well as some from @MarkKoz in-server.

I have updated the sources to include more comments, while also going through and cleaning up general structure/organisation and removing unused styles.

The discord link has been changed to be the first nav item, and a normal one now. I had to add some style overrides for the dropdown in order to get it to not slip off the ride side of the canvas when being viewed.

Som...

regal archBOT
ebon magnetBOT
#

Build 20201023.2 succeeded

Requested by

GitHub

Duration

00:02:37

Build pipeline

Site

regal archBOT
north knotBOT
ebon magnetBOT
#

Build 20201023.1 succeeded

Requested by

GitHub

Duration

00:04:45

Build pipeline

Bot

oak estuaryBOT
regal archBOT
#

Great job, this looks phenomenal!

One thing that stands out to me though is how the footer icons in the repository cards are spread out and centered. I'm used to it all being left aligned and close to each other, like a normal GitHub card:
image

I think I'd rather have the icons left aligned and close together, but I also wouldn't particularly mind it either way.

Everything is lo...

regal archBOT
#
[python-discord/bot] New branch created: mbaruh/mute
regal archBOT
regal archBOT
ebon magnetBOT
#

Build 20201023.3 succeeded

Requested by

GitHub

Duration

00:02:19

Build pipeline

Site

regal archBOT
ebon magnetBOT
#

Build 20201023.6 succeeded

Requested by

GitHub

Duration

00:02:07

Build pipeline

Site

regal archBOT
#
jb3
[python-discord/site] branch deleted: allow\-internal\-dns\-api
north knotBOT
ebon magnetBOT
#

Build 20201023.5 succeeded

Requested by

Joseph Banks

Duration

00:04:03

Build pipeline

Site

regal archBOT
north knotBOT
regal archBOT
ebon magnetBOT
#

Build 20201023.7 succeeded

Requested by

Joseph Banks

Duration

00:03:55

Build pipeline

Site

regal archBOT
ebon magnetBOT
#

Build 20201023.8 succeeded

Requested by

GitHub

Duration

00:02:15

Build pipeline

Site

regal archBOT
north knotBOT
#

Postgres backup completed!

regal archBOT