#Unable to verify with Github
9 messages · Page 1 of 1 (latest)
Project ID: 60eabf0b-947d-48d4-93ea-e47b04050f24
60eabf0b-947d-48d4-93ea-e47b04050f24
either too new or not active enough, there's nothing we can do as railway needs a verifiable github account
but railway is coming out with a hobby plan early next month that won't require these github verification checks, so look forward to those!
I think basing verification on both of these criteria is not the way to go. I have a 10+ old Github account, however my contributions have been spotty these last months as I mostly do open source work. I understand the need to have some usage limitations but the communication was not that good, as there has been a single email about upcoming changes taking effect on August 1st, however this verification process is still not clear enough.
I’ve been appreciative for the service for some small nodejs applications I have been running since 2022, but I think I must soon look for an alternative service. Unless I’m mistaken on the interpretation of the new usage rules
where you previously verified?