Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release - 0.2.0 #42

Merged
merged 43 commits into from Jun 21, 2021
Merged

Release - 0.2.0 #42

merged 43 commits into from Jun 21, 2021

Conversation

malparty
Copy link
Owner

Content

User web authentication with Devise.
Preview available in Staging

Features

Chores

N/A

Bugs

N/A

Rebase from setup deployment workflows
@malparty malparty added this to the 0.2.0 milestone Jun 21, 2021
@malparty malparty self-assigned this Jun 21, 2021
@malparty malparty added this to In development in Product backlog via automation Jun 21, 2021
protected

def update_allowed_parameters
devise_parameter_sanitizer.permit(:sign_up) do |u|

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Has the variable name 'u'

devise_parameter_sanitizer.permit(:sign_up) do |u|
u.permit(:first_name, :last_name, :email, :password, :password_confirmation)
end
devise_parameter_sanitizer.permit(:account_update) do |u|

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Has the variable name 'u'

# the authenticate method from devise documentation
def self.authenticate(email, password)
user = User.find_for_authentication(email: email)
user&.valid_password?(password) ? user : nil

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Is controlled by argument 'password'

login_as user, scope: :user
end

def sign_up_ui(email, password, password_confirm = nil)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Has approx 8 statements

@github-actions
Copy link

3 Errors
🚫 Brakeman static analysis detected issues in the code. If this is a false positive, mark it as such.
🚫 Code coverage data not found
🚫 Undercover: coverage report cannot be found.

BRAKEMAN REPORT

Application path Rails version Brakeman version Started at Duration
/home/runner/work/google-search-ruby/google-search-ruby 6.1.3.1 5.0.1 2021-06-21 05:19:43 +0000 2.179770558 seconds
Checks performed
BasicAuth, BasicAuthTimingAttack, CSRFTokenForgeryCVE, ContentTag, CookieSerialization, CreateWith, CrossSiteScripting, DefaultRoutes, Deserialize, DetailedExceptions, DigestDoS, DynamicFinders, EscapeFunction, Evaluation, Execute, FileAccess, FileDisclosure, FilterSkipping, ForgerySetting, HeaderDoS, I18nXSS, JRubyXML, JSONEncoding, JSONEntityEscape, JSONParsing, LinkTo, LinkToHref, MailTo, MassAssignment, MimeTypeDoS, ModelAttrAccessible, ModelAttributes, ModelSerialize, NestedAttributes, NestedAttributesBypass, NumberToCurrency, PageCachingCVE, PermitAttributes, QuoteTableName, Redirect, RegexDoS, Render, RenderDoS, RenderInline, ResponseSplitting, RouteDoS, SQL, SQLCVEs, SSLVerify, SafeBufferManipulation, SanitizeMethods, SelectTag, SelectVulnerability, Send, SendFile, SessionManipulation, SessionSettings, SimpleFormat, SingleQuotes, SkipBeforeFilter, SprocketsPathTraversal, StripTags, SymbolDoSCVE, TemplateInjection, TranslateBug, UnsafeReflection, UnsafeReflectionMethods, ValidationRegex, VerbConfusion, WithoutProtection, XMLDoS, YAMLParsing

SUMMARY

Scanned/Reported Total
Controllers 2
Models 2
Templates 17
Errors 0
Security Warnings 1 (0)
Warning Type Total
Cross-Site Scripting 1

SECURITY WARNINGS

Confidence Class Method Warning Type Message
Medium Cross-Site Scripting loofah gem 2.10.0 is vulnerable (CVE-2018-8048). Upgrade to 2.2.1 near line 214

Generated by 🚫 Danger

fill_in 'user_last_name', with: user.last_name
fill_in 'user_email', with: email
fill_in 'user_password', with: password
fill_in 'user_password_confirmation', with: password_confirm || password

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Is controlled by argument 'password_confirm'

Product backlog automation moved this from In development to Ready for QA Jun 21, 2021
@junan
Copy link
Contributor

junan commented Jun 21, 2021

@malparty I think we don't need Content section.

In compass release we add Content section(where we add content type PRs) also because we in the compass repo we have content type of issue/PR besides feature, chore, bug, release type of issue/PR . Most of the our projects we only have release, feature, chore, bug type.

@malparty
Copy link
Owner Author

@malparty I think we don't need Content section.

In compass release we add Content section(where we add content type PRs) also because we in the compass repo we have content type of issue/PR besides feature, chore, bug, release type of issue/PR . Most of the our projects we only have release, feature, chore, bug type.

Thanks! Time saver for future releases!! :) :) :)

@malparty malparty merged commit 6ce1fed into main Jun 21, 2021
@malparty malparty moved this from Ready for QA to Completed in Product backlog Jun 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging this pull request may close these issues.

None yet

3 participants