Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: update 2024 finance info #3652

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

derberg
Copy link
Member

@derberg derberg commented Feb 5, 2025

update all 2024 finance info

Summary by CodeRabbit

  • New Features

    • Expanded expense tracking with new categories for November, including "Swag Store", "Community Manager", "Community Marketing Specialist", and "JSON Schema Sponsorship".
    • Enhanced December budgeting by introducing additional expense categories, including "Bounty Program", "Swag Store", "Community Manager", "Community Marketing Specialist", "JSON Schema Sponsorship", and "AsyncAPI Conf on Tour 2024".
  • Bug Fixes

    • Removed outdated categories from the expenses link, streamlining the expense tracking process.
  • Updates

    • Adjusted amounts for existing categories, including modifications to the "Mentorship Program 2023" and "AsyncAPI Conf on Tour 2023".

Copy link
Contributor

coderabbitai bot commented Feb 5, 2025

Walkthrough

The configuration files for financial expenses have been updated to reflect changes in amounts for existing categories and the addition of new entries for November and December 2024. The "Mentorship Program 2023" category has undergone specific adjustments in earlier months, while multiple new categories have been introduced for the last two months of the year. Additionally, several categories were removed from the ExpensesLink.yml file.

Changes

File Summary
config/finance/2024/Expenses.yml Updated amounts for "Mentorship Program 2023" in February, March, and April; removed May entry. Added new entries for November (Swag Store: 472.36, Community Manager: 2000.00, Community Marketing Specialist: 2000.00, JSON Schema Sponsorship: 250.00) and December (Bounty Program: 1400.00, Swag Store: 917.99, Community Manager: 2000.00, Community Marketing Specialist: 2000.00, JSON Schema Sponsorship: 250.00, AsyncAPI Conf on Tour 2024: 2767.99).
config/finance/2024/ExpensesLink.yml Removed multiple categories including "Ambassador Program," "Google Season of Docs 2023," "Swag Store," "Bounty Program," "3rd Party Services," "Community Manager," "AsyncAPI Conf on Tour 2023," "AsyncAPI Conf on Tour 2024," "Mentorship Program 2023," and "JSON Schema Sponsorship." Minor formatting change to "Community Marketing Specialist."

Possibly related PRs

Suggested labels

ready-to-merge

Poem

I'm a rabbit with a joyful hop,
Digging in numbers, I never stop.
New expenses sprout like carrots in spring,
November, December, hear the code sing!
Bytes and binkies, a merry rhythm in every hop.
🥕🐇

Tip

🌐 Web search-backed reviews and chat
  • We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
  • You can disable this feature by setting web_search: false in the knowledge_base settings.
  • Please share any feedback in the Discord discussion.

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4489719 and 03ebb1a.

📒 Files selected for processing (1)
  • config/finance/2024/ExpensesLink.yml (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • config/finance/2024/ExpensesLink.yml
⏰ Context from checks skipped due to timeout of 180000ms (4)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Lighthouse CI

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Feb 5, 2025

Deploy Preview for asyncapi-website ready!

Name Link
🔨 Latest commit 03ebb1a
🔍 Latest deploy log https://app.netlify.com/sites/asyncapi-website/deploys/67a4829667c2180008190d07
😎 Deploy Preview https://deploy-preview-3652--asyncapi-website.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@derberg
Copy link
Member Author

derberg commented Feb 5, 2025

no need to review yet, I'm still doing double review

Copy link

codecov bot commented Feb 5, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (1c0a3aa) to head (03ebb1a).

Additional details and impacted files
@@            Coverage Diff            @@
##            master     #3652   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           20        20           
  Lines          732       732           
=========================================
  Hits           732       732           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
config/finance/2024/Expenses.yml (1)

132-144: December Expense Entries Added Correctly with Minor Formatting Issue

The December section adds six expense entries, including the new event "AsyncAPI Conf on Tour 2024", which aligns well with the existing YAML structure. However, the static analysis tool flagged a missing newline character at the end of the file (line 144). Please ensure a newline is added at the end to conform with YAML best practices.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 144-144: no new line character at the end of file

(new-line-at-end-of-file)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9cc9ec1 and 7f183ac.

📒 Files selected for processing (1)
  • config/finance/2024/Expenses.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
config/finance/2024/Expenses.yml

[error] 144-144: no new line character at the end of file

(new-line-at-end-of-file)

⏰ Context from checks skipped due to timeout of 180000ms (4)
  • GitHub Check: Redirect rules - asyncapi-website
  • GitHub Check: Header rules - asyncapi-website
  • GitHub Check: Pages changed - asyncapi-website
  • GitHub Check: Lighthouse CI
🔇 Additional comments (1)
config/finance/2024/Expenses.yml (1)

123-131: November Expense Entries Added Correctly

The newly added November section includes entries for "Swag Store", "Community Manager", "Community Marketing Specialist", and "JSON Schema Sponsorship" with their respective amounts, and the YAML structure is consistent with the previous months. Please verify that these amounts and categories match the updated financial information for November 2024.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
config/finance/2024/ExpensesLink.yml (1)

31-33: Formatting Issues with "Community Marketing Specialist" Entry
The "Community Marketing Specialist" entry appears to have been reformatted rather than removed. However, YAMLlint reports two issues:

  • Trailing spaces on the last line (line 33).
  • Missing newline at the end of the file.

Please remove any trailing spaces and ensure that the file ends with a newline to conform with YAML standards.

Suggested diff:

-  link: "https://github.com/orgs/asyncapi/discussions/1176"
-  
+  link: "https://github.com/orgs/asyncapi/discussions/1176"

Ensure that the final file ends with a newline.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 33-33: no new line character at the end of file

(new-line-at-end-of-file)


[error] 33-33: trailing spaces

(trailing-spaces)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 235134b and b7787fb.

📒 Files selected for processing (2)
  • config/finance/2024/Expenses.yml (3 hunks)
  • config/finance/2024/ExpensesLink.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
config/finance/2024/ExpensesLink.yml

[error] 33-33: no new line character at the end of file

(new-line-at-end-of-file)


[error] 33-33: trailing spaces

(trailing-spaces)

config/finance/2024/Expenses.yml

[error] 145-145: no new line character at the end of file

(new-line-at-end-of-file)


[error] 145-145: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 180000ms (1)
  • GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (16)
config/finance/2024/ExpensesLink.yml (10)

1-3: Removal of "Ambassador Program" Category
The removal of the "Ambassador Program" entry is consistent with the updated 2024 financial information. Please make sure that any cross-references to this category in related files (for example, in Expenses.yml) have been updated accordingly.


4-6: Removal of "Google Season of Docs 2023" Category
The "Google Season of Docs 2023" entry has been removed as part of the update. Ensure that any dependent data in other finance files is in sync with this deletion.


7-9: Removal of "Swag Store" Category
The deletion of the "Swag Store" entry is straightforward. Confirm that any financial reporting or aggregations relying on it have been adjusted.


10-12: Removal of "Bounty Program" Category
The "Bounty Program" category removal appears intentional. Verify that its removal does not adversely affect linked financial summaries.


13-15: Removal of "3rd Party Services" Category
Removing the "3rd Party Services" category aligns with the update objective. Ensure that any historical data or related references are handled appropriately.


16-18: Removal of "Community Manager" Category
The deletion of the "Community Manager" entry is clear. Please double-check that the related financial documents no longer reference this category.


19-21: Removal of "AsyncAPI Conf on Tour 2023" Category
The "AsyncAPI Conf on Tour 2023" category has been removed. Verify that financial consolidations elsewhere reflect this change.


22-24: Removal of "AsyncAPI Conf on Tour 2024" Category
The removal of the "AsyncAPI Conf on Tour 2024" entry is noted. Ensure that any planning or reporting dependent on this data is updated.


25-27: Removal of "Mentorship Program 2023" Category
The deletion of the "Mentorship Program 2023" entry is in line with the overall updates. Please verify that its removal is correctly propagated to other financial summaries (e.g., in Expenses.yml).

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 27-27: trailing spaces

(trailing-spaces)


28-30: Removal of "JSON Schema Sponsorship" Category
The "JSON Schema Sponsorship" category has been removed appropriately. As with the other removals, cross-check any impacted references in related files.

config/finance/2024/Expenses.yml (6)

23-24: Update Mentorship Program 2023 February Amount
The amount for the "Mentorship Program 2023" in February has been updated to '4125.00'. Please verify that this figure accurately reflects the intended 2024 financial update.


30-31: Adjust March Amount for Mentorship Program 2023
The March entry now shows an amount of '2475.00' for the "Mentorship Program 2023". Confirm that this decreased value correctly aligns with the revised financial data.


41-42: Update April Amount for Mentorship Program 2023
The April entry for "Mentorship Program 2023" is updated to '2475.00'. Please ensure this change is consistent with the updated financial information and overall year-long adjustments.


115-122: Review October Financial Entries
In October, the "AsyncAPI Conf on Tour 2024" amount has been modified from '962.01' to '289.78', and new entries for "Community Manager", "Community Marketing Specialist", and "JSON Schema Sponsorship" have been added. Verify that these adjustments are correct and consistent with the updated financial guidelines for 2024.


123-125: Add New November Entry for Swag Store
A new November entry for "Swag Store" with an amount of '472.36' has been added. Please confirm that this new entry, alongside the other November records, fully reflects the updated financial structure for the month.


132-145: 🛠️ Refactor suggestion

Introduce December 2024 Financial Entries & Address YAML Formatting
The December section introduces new financial entries with the following amounts:

  • Bounty Program: '1400.00'
  • Swag Store: '917.99'
  • Community Manager: '2000.00'
  • Community Marketing Specialist: '2000.00'
  • JSON Schema Sponsorship: '250.00'
  • AsyncAPI Conf on Tour 2024: '2767.99'

Please verify that these entries are correct per the updated financial information for December 2024.

Static Analysis Note: YAMLlint has flagged that line 145 has trailing spaces and is missing a newline at the end of the file. Ensuring that the file ends with a clean newline without trailing spaces will help maintain consistency and prevent linting errors.

A suggested diff for addressing the static analysis issues:

-    Amount: '2767.99'
-    
+    Amount: '2767.99'

and ensure that there is a newline at the end of the file.

✅ Verification successful

Error: No shell scripts or web queries found


Verification Successful: December 2024 Entries & YAML Formatting

The December section now accurately reflects the updated financial data. Please remove the trailing spaces on line 145 and ensure the file ends with a newline to resolve the YAMLlint issues.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 145-145: no new line character at the end of file

(new-line-at-end-of-file)


[error] 145-145: trailing spaces

(trailing-spaces)

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 316bd0d and 4489719.

📒 Files selected for processing (1)
  • config/finance/2024/ExpensesLink.yml (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
config/finance/2024/ExpensesLink.yml

[error] 23-23: no new line character at the end of file

(new-line-at-end-of-file)


[error] 23-23: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 180000ms (1)
  • GitHub Check: Test NodeJS PR - macos-13
🔇 Additional comments (1)
config/finance/2024/ExpensesLink.yml (1)

1-20: Streamline Outdated Expense Categories

The diff shows that several outdated categories (e.g., "Ambassador Program", "Google Season of Docs 2023", "Swag Store", etc.) have been removed. This cleanup appears to be in line with updating the financial information for 2024. Please ensure that these removals are coordinated with related configuration files (for instance, verifying that any necessary details now reside in the Expenses.yml file) to avoid any discrepancies in category references or financial data.

Comment on lines 30 to 23
- category: "Community Marketing Specialist"
link: "https://github.com/orgs/asyncapi/discussions/1176" No newline at end of file
link: "https://github.com/orgs/asyncapi/discussions/1176"

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Verification agent

🧩 Analysis chain

Verify "Community Marketing Specialist" Entry and Fix Formatting

The AI summary indicates that the "Community Marketing Specialist" entry should remain unchanged, yet the diff suggests a deletion or modification of the entry (line 21 shows a removal marker and lines 22–23 show minor changes). Please confirm that this entry remains present as intended for accurate reporting. Additionally, YAMLlint flagged two formatting issues:

  • Missing newline at end of file: Please ensure the file ends with a newline.
  • Trailing spaces on the last line: Remove any extra whitespace.

A suggested diff for the formatting fixes:

-  
\ No newline at end of file
+  

**


Error: No shell scripts or web queries found


🏁 Script executed:

#!/bin/bash
FILE="config/finance/2024/ExpensesLink.yml"

echo "Checking file: $FILE"
if [[ ! -f $FILE ]]; then
  echo "File $FILE does not exist."
  exit 1
fi

echo "---- Excerpt (lines 21-23) ----"
sed -n '21,23p' "$FILE"

echo "---- Verifying 'Community Marketing Specialist' entry ----"
grep -n "Community Marketing Specialist" "$FILE" || echo "'Community Marketing Specialist' entry not found!"

echo "---- Checking for newline at the end of the file ----"
# Tail returns nothing if the file ends with a newline.
if [ -z "$(tail -c 1 "$FILE")" ]; then
    echo "File ends with a newline."
else
    echo "No newline at end of the file."
fi

echo "---- Checking for trailing whitespace ----"
grep -nE "[[:blank:]]+$" "$FILE" || echo "No trailing whitespace found."

Length of output: 1120

Action: Fix YAML Formatting Issues in config/finance/2024/ExpensesLink.yml

  • The "Community Marketing Specialist" entry is present and remains unchanged.
  • The file is missing a newline at the end.
  • There are trailing spaces at the end of the file (line 23).

Please update the file by removing the extra whitespace and ensuring it ends with a newline.

🧰 Tools
🪛 YAMLlint (1.35.1)

[error] 23-23: no new line character at the end of file

(new-line-at-end-of-file)


[error] 23-23: trailing spaces

(trailing-spaces)

@derberg
Copy link
Member Author

derberg commented Feb 5, 2025

@akshatnema I'm too stupid for this yaml neat peak from rabbit. Adding new line, removing - always the same - can we ignore it 😄 or do you have a solution?

@derberg
Copy link
Member Author

derberg commented Feb 6, 2025

/ptal

@asyncapi-bot
Copy link
Contributor

@magicmatatjahu @devilkiller-ag @akshatnema @sambhavgupta0705 @anshgoyalevil @Mayaleeeee Please take a look at this PR. Thanks! 👋

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants