Fix for duplicate channels

Author: StephanAkkerman

CONTRIBUTING.md

@@ -1,8 +1,8 @@
-# Job Openings Automated Guidelines
+# FinTwit-Bot Guidelines
 
 ## Code Formatting and Linting
 
-Job Openings Automated uses [Black](https://black.readthedocs.io/en/stable/index.html) with default values for automatic code formatting, along with [ruff](https://docs.astral.sh/ruff/). We also use [NumPy-style docstrings](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_numpy.html) for documenting the code. As part of the checks on pull requests, it is checked whether the code still adheres to the code style. To ensure you don't need to worry about formatting and linting when contributing, it is recommended to set up the following:
+FinTwit-Bot uses [Black](https://black.readthedocs.io/en/stable/index.html) with default values for automatic code formatting, along with [ruff](https://docs.astral.sh/ruff/). We also use [NumPy-style docstrings](https://sphinxcontrib-napoleon.readthedocs.io/en/latest/example_numpy.html) for documenting the code. As part of the checks on pull requests, it is checked whether the code still adheres to the code style. To ensure you don't need to worry about formatting and linting when contributing, it is recommended to set up the following:
 
 - Integration in VS Code:
   - For [Black](https://marketplace.visualstudio.com/items?itemName=ms-python.black-formatter)
@@ -42,17 +42,21 @@ When submitting a pull request, please follow these guidelines:
 To ensure a smooth and transparent merging process, we have established the following policy for merging pull requests:
 
 1. **Review and Approval**:
+
    - Pull requests must be reviewed and approved by at least one project maintainer.
    - Reviews from other contributors are encouraged but not required.
 
 2. **Passing Checks**:
+
    - All pull requests must pass continuous integration (CI) checks, including tests and linters.
    - Ensure there are no merge conflicts with the `main` branch.
 
 3. **Documentation**:
+
    - If your pull request introduces new features or changes existing functionality, update the relevant documentation.
 
 4. **Labeling**:
+
    - Use appropriate labels (e.g., `bug`, `enhancement`, `documentation`) to categorize the pull request.
 
 5. **Merging**:
@@ -62,25 +66,30 @@ To ensure a smooth and transparent merging process, we have established the foll
 ## Branch Management Policy
 
 1. **Branch Naming Conventions**:
+
    - Use descriptive names for your branches to make it clear what feature or fix is being worked on.
    - Common prefixes include `feature/`, `bugfix/`, `hotfix/`, and `chore/`.
    - Example: `feature/add-login-page`, `bugfix/fix-navbar-issue`.
 
 2. **Creating Branches**:
+
    - Always create branches from the latest version of the `main` branch.
    - Use short-lived branches for new features, bug fixes, or any changes to the codebase.
 
 3. **Pull Requests**:
+
    - Ensure your branch is up-to-date with `main` before opening a pull request.
    - Provide a clear and detailed description of the changes in your pull request.
    - Link to any relevant issues or discussions.
 
 4. **Merging Branches**:
+
    - Ensure all CI checks pass before merging.
    - Preferably use "Squash and merge" to maintain a clean commit history.
    - Obtain necessary approvals from maintainers or reviewers before merging.
 
 5. **Deleting Merged Branches**:
+
    - After a branch has been successfully merged into `main`, it should be deleted.
    - This helps keep the repository clean and reduces clutter.
    - You can delete the branch directly on GitHub after merging, or use the following Git command:

curl_example.txt

@@ -1,5 +1,5 @@
 Replace all contents of this file with the following:
-1. Go to Twitter.com
+1. Go to x.com (using Chrome as browser, otherwise the cURL will be a different format)
 2. Login
 3. On the home timeline (click on following) press F12, this will open devtools in Chrome
 4. Go to the Network section

src/util/disc.py

@@ -125,25 +125,32 @@ async def get_channel(
         The discord.TextChannel object of the channel with the given name.
     """
 
+    # Loop over all the guilds the bot is in
     for guild in bot.guilds:
+        # Find the guild with the given name from the .env file
         if guild.name == guild_name:
+            # Loop over all the channels in the guild
             for channel in guild.channels:
+                # Find the channel with the given name
                 if channel.name == channel_name:
+                    # If there is no given category name return the first one
                     if category_name is None:
                         return channel
                     else:
+                        # Otherwise find it in the given category
                         if channel.category:
                             if channel.category.name == category_name:
                                 return channel
 
-    logger.info(
+    logger.warning(
         f"Channel named: {channel_name}, with category {category_name} not found in guild: {guild_name}.\nCreating it..."
     )
 
-    # If the channel is not found, create it
+    # If the channel is not found, create it (with a category if given)
     if category_name:
         category = discord.utils.get(guild.categories, name=category_name)
         channel = await guild.create_text_channel(channel_name, category=category)
+        return channel
 
     # Maybe read the category from the config file
     channel = await guild.create_text_channel(channel_name)