Actions: vjik/telegram-bot-api
Actions
64 workflow runs
64 workflow runs
CurlTransport
cs fixer
#66:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#65:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#64:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#63:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#62:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#61:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#60:
Pull request #142
synchronize
by
vjik
FailResult::$errorCode
type to int|null
cs fixer
#59:
Pull request #143
synchronize
by
vjik
FailResult::$errorCode
type to int|null
cs fixer
#58:
Pull request #143
synchronize
by
vjik
FailResult::$errorCode
type to int|null
cs fixer
#57:
Pull request #143
opened
by
vjik
CurlTransport
cs fixer
#56:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#55:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#54:
Pull request #142
synchronize
by
vjik
CurlTransport
cs fixer
#53:
Pull request #142
opened
by
vjik
TelegramBotApi
to internal Api
class
cs fixer
#51:
Pull request #140
opened
by
vjik
MethodInterface::getResultType()
to ValueProcessorInterface
cs fixer
#50:
Pull request #139
synchronize
by
vjik
MethodInterface::getResultType()
to ValueProcessorInterface
cs fixer
#49:
Pull request #139
opened
by
vjik
ObjectFactory
refactoring
cs fixer
#46:
Pull request #136
synchronize
by
vjik
ObjectFactory
refactoring
cs fixer
#45:
Pull request #136
synchronize
by
vjik
ObjectFactory
refactoring
cs fixer
#44:
Pull request #136
synchronize
by
vjik
ObjectFactory
refactoring
cs fixer
#43:
Pull request #136
synchronize
by
vjik
ObjectFactory
refactoring
cs fixer
#42:
Pull request #136
synchronize
by
vjik