The current flow of praying through the journal is not as distraction-free as I had hoped. My vision is for a process that eliminates everything on the screen, and displays requests one-at-a-time. Requests can be marked as prayed, and also flagged for follow-up. The follow-up state should be scoped to the user's session, and should be cleared once any other action occurs with a request.
The current flow of praying through the journal is not as distraction-free as I had hoped. My vision is for a process that eliminates everything on the screen, and displays requests one-at-a-time. Requests can be marked as prayed, and also flagged for follow-up. The follow-up state should be scoped to the user's session, and should be cleared once any other action occurs with a request.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The current flow of praying through the journal is not as distraction-free as I had hoped. My vision is for a process that eliminates everything on the screen, and displays requests one-at-a-time. Requests can be marked as prayed, and also flagged for follow-up. The follow-up state should be scoped to the user's session, and should be cleared once any other action occurs with a request.