Community support is offered through the following channels. These channels are monitored regularly, but response time is not guaranteed. If you need immediate help with MassTransit, consider Commercial Support.
There is a MassTransit tag on Stack Overflow, which has many questions that have already been asked. Several developers regularly monitor this tag for new questions, so that's a great place to start. Be sure to search and see if your question has already been asked, that is the fastest way to an answer if someone else has already experienced the same issue.
Before you just post your question, however, spend a few moments to compose your thoughts and formulate your question. There is nothing as pointless as simply telling us "MassTransit does not work for me" with no further information to give any clue to why. Before you post, search the web to see if your question has already been asked or even answered. And if it has been, you will already have your answer.
Questions, ideas, and suggestions can be posted on GitHub Discussions. Similar to Stack Overflow, but integrated with GitHub, this is a great place to post code samples, share ideas, and get help using MassTransit. The same guidelines above apply to discussions.
If you have an issue using MassTransit, this is the place to start before creating an issue.
MassTransit has an active Discord server, which is a great place to get quick answers to short questions as well as share in engaging conversations about MassTransit, messaging, or whatever.
There are several seasons of videos available on YouTube, and new episodes are added fairly regularly. There are also many short-format Commutes that cover quick topics.
You might be able to get some attention on Twitter, and you're highly encouraged to tweet about MassTransit. Feel free to tag
@mtproj (strangely, MassTransit is a noisy search term -- go figure).
Please do not open an issue on GitHub, unless you have spotted an actual bug in MassTransit. If you are unsure, pursue one of the alternate options first. If we confirm it's a bug, we'll ask you to create the issue.
Issues are not the place for questions, and they'll likely be closed.
This policy is in place to avoid bugs being drowned out in a pile of sensible suggestions for future enhancements and calls for help from people who forget to check back if they get it and so on.