Thanks for using giscoR! Before filing an issue, there are a few places to explore and details to prepare so the process goes smoothly.
Make a reprex
Start by making a minimal reproducible example using the reprex package. If you have not used reprex before, it is worth learning because it makes R questions easier to answer. For additional reprex pointers, see the Get help! section of the tidyverse site.
Where to ask?
Armed with your reprex, the next step is to figure out where to ask.
If it is a question, start with community.rstudio.com or Stack Overflow. There are more people there to answer questions.
If it is a bug, you are in the right place: file an issue.
If you are not sure, let the community help you figure it out. If your problem is a bug or a feature request, you can return here and report it.
Before opening a new issue, search issues and pull requests to make sure the bug has not been reported or already fixed in the development version. By default, the search will be pre-populated with is:issue is:open. You can edit the qualifiers (e.g. is:pr, is:closed) as needed. For example, remove is:open to search all issues in the repo, open or closed.
What happens next?
To be as efficient as possible, development of rOpenGov packages often happens in focused bursts, so you should not worry if you do not get an immediate response. We typically review a repo after enough issues accumulate, then focus our efforts on that repo. That makes development more efficient because it avoids expensive context switching between problems, at the cost of taking longer to get back to you. This process makes a good reprex particularly important because it might be multiple months between your initial report and when we start working on it. If we cannot reproduce the bug, we cannot fix it.