This job will only be used to get new issues. We will create another job to update the information of pre-existing issues in a future PR.
I added a piece of code to require a username and password when trying to access the Sidekiq dashboard in production. I'll try it out when this is merged and I've deployed. I'll also see if I can schedule this job with Heroku scheduler once I've deployed.
This PR sets up Sidekiq (https://github.com/Contributees/First-Ruby-Quest/issues/5) and moves the logic we had to make the API call and create Issues from the Issue model to a Sidekiq job.
This job will only be used to get new issues. We will create another job to update the information of pre-existing issues in a future PR.
I added a piece of code to require a username and password when trying to access the Sidekiq dashboard in production. I'll try it out when this is merged and I've deployed. I'll also see if I can schedule this job with Heroku scheduler once I've deployed.